| Target release | Release name or number |
|---|---|
| Epic | |
| Document status | |
| Priority | |
| eLMIS Status | Partially Implemented |
| OpenLMIS Status | Not Implemented |
| PATH | |
| OpenLMIS | |
| JSI |
|
Ability to allow the users to view/update their own profile
Status in eLMIS: Partially Implemented.
Status in OpenLMIS: Not Implemented
Priority: High priority across implementations
There are a number of cross-cutting features that request SMS integration. We would like to consolidate these features into an integration that utilizes best in class SMS systems like RapidPro.
| # | Title | User Story | Label | Importance | Notes | JIRA Tickets |
|---|---|---|---|---|---|---|
| 1 | Users | Time box for one specific notification or use case to show value versus implementing a full suite of things. | ||||
Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.
Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.
| Description | Link |
|---|---|
| None at this time | Link to JIRA |
Initial communication between stakeholders and the development team to help understand scope and estimates.
Below is a list of questions to be addressed as a result of this requirements document:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 |