...
To evaluate the best technology and channels to enable end-users to feedback about the UX
Page Properties | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
|
Background
The Open Hospital user base is typically offline and tech-unaware, it very rare that they want to reach out and report a bug, an issue, or any comment.
...
Whenever the amount of support requests can be low or high, the point to consider is “who” will handle the such requests and the details provided could be very poor or totally lacking of useful info to handle the problem reported (in other words, poorly documented Jira’s issues)
Options considered
Option 1: | Option 2: | |
---|---|---|
Description | Jira Issue collectors | Jira Service Desk + Issue collectors |
Pros and cons | Integrated with Jira Embeddable in the UI and the Website |
Feedback from end-users go directly to backlog as new issues | Integrated with Jira Embeddable in the UI and the Website Issues can be triaged Requires a separate Jira project | |||||||||||||
Estimated cost |
|
|
---|
Action items
- To test Option 1 (integration with Jira) Tsognong FidèleAlessandro Domanico
- To test Option 2 (Service Desk project) Tsognong FidèleAlessandro Domanico