Versions Compared

Version Old Version 13 New Version Current
Changes made by

Nick Reid (Deactivated)

Nick Reid (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page Properties


Target release3.2
Ticket

Jira Legacy
serverJIRA (openlmis.atlassian.net)
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-2187

Document status

Status
colourYellow
titleIn Dev

Document owner
Mary Jo Kochendorfer (Deactivated)
Technical LeadNick Reid (Deactivated)


Goals/Scope

  • Provide a way to review and edit information on the requested and calculated order quantities across multiple requisitions waiting for approval. 
  • Ability to see total cost for the selected requisitions (batch of requisitions in the view) to support budgetary decision making.
  • Allow for review of requisitions from all facilities within a geographic/administrative area

...

#IssueResolution
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?



Open Tickets

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = OLMIS AND status in (Roadmap, "To Do") AND labels = BatchApprove
serverId448ba138-230b-3f91-a83e-16e7db1deed1

Diagrams

Here is a high-level overview of the batch approval process:

...