...
| # | Question | Outcome | Status | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Is
| SMS needs to be included in the feature set. Multiple countries mentioned that cost is not a concern as phone companies provide messages for free. | Answered | ||||||||||
| 2 | If SMS is no longer required - are there any requirements in Notifications - Push Reminders that we will need to support? Push notifications from an admin to all users happen through JIRA. Is this enough? | Only user stories 1 and 2 are required for the initial version. | Answered | ||||||||||
| 3 | Phone numbers are already captured in User Profile page - but there is only minimal validation on format. Is this required? It would be required if SMS is included in this feature. | Phone number format validation needs to be updated. | Answered | ||||||||||
| 4 | Need to research solutions for customizing messages in other languages | Messages need to be configurable but not localized | Answered | ||||||||||
| 5 | Who is the user that logs in occasionally? Do they need to receive notifications to remind them to log in and check something? | Understanding this user will help us ensure we support notification scenarios for this user. | Wesley Brown to confirm | ||||||||||
| 6 | Are there more types of notifications that could be categorized as high level? | Helps us understand which notifications would override a user's opt-out preferences. | Wesley Brown to confirm (maybe with help from Nikodem Graczewski (Unlicensed) to understand current state - emergency requisitions, reset password, are there others?) | ||||||||||
| 7 | Should we classify types of notifications so that we all agree on terms to use? Informative notifications: Notifications Requisition status updates (would notifications about upcoming system updates, planned system outages , (maybe also include requisition status updates be included in this typeclassification?) Action-based (action-oriented) notifications: Notifications that require the user to log into OpenLMIS to take action, some action-based notifications would override the user's notification preferences such as emergency requisitions or reset password email notifications. Time-bound notifications (or reminder notifications?): Notifications that remind a user something needs to be done, or hasn't been done yet - should be done Are there default settings for each notification class that would be acceptable?
What classifications should be used for notifications of system updates or planned system outages? This is a message that is configured by an administrator and then set to all users. (Malawi example, or is slack good enough?). | Gain agreement on terminology so we understand what notifications are supported and must be supported. Helps explain the value and use for each type. | Sam Im (Deactivated): This is a design discussion. This does not mean that notifications must be designed with a classification but is used to help us understand the value of notifications for each user. FYI Wesley Brown | ||||||||||
| 8 | What are other generalized needs for requisitions and stock management (future design) | ||||||||||||
| 9 | Are we supporting fulfillment notifications in 3.6 scope? | Wesley Brown to confirm (maybe with help from Nikodem Graczewski (Unlicensed) to understand current state of fulfillment type notifications) |
...