...
# | Title | User Story | Label | Importance | Notes | JIRA Ticket |
---|
1 | Batch Approval for Requisitions | As a district-level (or any mid-level) requisition approver, I want to review and adjust all the requisitions for my supervisory node at once So that I can more efficiently review, adjust approved quantities, and fit within budget guidelines. - able to see the total order quantities and cost for all the facilities selected so that I can ensure the total is within the district budget.
- see what each facility is requesting per commodity so that I can make adjustments to ensure the total is within the district budget.
- total costs update when adjustments are made
| Malawi | Nice to have | | Core placeholder, implemented in Malawi Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2187 |
---|
|
|
Open Questions
# | Issue | Resolution |
---|
1 | Really large table The batch requisition screen can be extremely large. Malawi estimates that a DIVO might have 20 facilities to approve, and some programs with over 300 orderables. There is no internal navigation to orient the user (ie how does a user find a specific orderable, or facility) - Would a user want to search, sort, or filter the list of orderables
- Is there a simpler way to display so much data
- Can groups of data be made to allow a user to "open" collapsible areas of content
- Would adding pagination to the table make it easier for a user to read and understand?
|
|
|
|
|
Diagrams
Here is a high-level overview of the batch approval process:
...