| Target release | Release name or number |
|---|---|
| Epic | Requisition - Product Display |
| Document status | |
| Priority | |
| eLMIS Status | Implemented |
| OpenLMIS Status | Implemented |
| PATH | |
| OpenLMIS | Mary Jo Kochendorfer (Deactivated) |
| JSI | Ashraf Islam (Unlicensed) |
|
Ability to control how a product is displayed on R&R form. Typical R&R contains categories are subcategories and products are displayed under such sections. A specific product can be under one category in one R&R and under another in a different R&R. Similarly, a product can be a full supply product in program and a non-full supply in another program.
Status in eLMIS: Implemented.
Status in OpenLMIS: Implemented but not available via UI (only csv upload)
Priority: High priority for Tanzania, Zanzibar, Zambia
Product attributes needs to be settable in such as way that it's display on different R&R forms can be controlled.
Printed R&R forms are available to show how a product needs to be configured to mimic paper forms on the on-line data entry screens
User Stories
| # | Title | User Story | Label | Importance | Notes | JIRA Tickets |
|---|---|---|---|---|---|---|
| 1 | R&R form | As an administrator I want to be able to configure products under specific categories so that it mimic paper R&R forms. | R&R form | Must have | See eLMIS screenshot below | |
| 2 | Product form | As an administrator I want to be able to set product attributes to control how they appear on the R&R form | Product form | Must have | See eLMIS screenshot below | |
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 |
|---|---|
| Name of story or release | 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 |