Android - Send support feedback to Zendesk

Description

See https://openedx.atlassian.net/wiki/display/MA/Learner+and+Partner+Support+Enhancements for additional thoughts. Specifically, the idea of sending the information to Zendesk directly by calling its API, rather than indirectly through email.

Requested data that would be useful for support:

  • edX app version #

  • OS version #

  • Device Type

  • Username/Email

  • Device information, such as RAM, etc

  • List of user's courses (optionally sent?). If above a certain threshold, only the number of courses can be sent.

Steps to Reproduce

None

Reason for Variance

None

Release Notes

None

Activity

Show:
Christopher Lee
February 3, 2016, 3:15 PM

For this particular ticket, should we just add some of this information to the body while the zendesk stuff is still being figured out by ? I think this change would be very simple and a good interim solution.

Derek Hixon
February 3, 2016, 8:52 PM

I think adding to the body now makes most sense - and can asses later down the road, don't want to hold anything up though.

Christopher Lee
February 4, 2016, 1:49 PM

FYI

Nimisha Asthagiri
February 4, 2016, 3:32 PM

Makes sense. For the email, since we would be pre-populating the email body with diagnostic information, we'll need to make sure it is still inviting for users to enter their information. So the body should be formatted such that the diagnostic information is displayed as footer information, for example.

And, we'll want to only include a subset of the data we listed in this ticket. Perhaps only the following:
edX app version # (e.g., 2.0.0.1)
Device Type (Android or iOS)

For Android, it may be useful to include their device information as well.

Since the UserAgent string contains all this information, just sending the UserAgent value may be enough (if available to the app code). But we should make sure it's not a deterrent since it includes more than the above list.

Brian Guertin
February 12, 2016, 1:18 PM

I agree with , calling an API makes more sense here. And it looks like there is already code to do it on the server, so should be pretty easy to do.

Assignee

Unassigned

Reporter

Michael Katz

Labels

Customer

None

URL

None

Groups with Read-Only Access

None

Actual Points

None

Reach

None

Impact

None

Open edX Discourse Thread

None

Platform Map Area (Levels 1 & 2)

None

Platform Map Area (Levels 3 & 4)

None

Contributor Name

None

Blended Project Status Page

None

edX Squad

None

Product Rollout Framework

None

Content & Partner Success Lead

None

Marketing Lead

None

Learning Lead

None

Support Lead

None

Fix versions

Priority

Unset
Configure