Backlog Grooming Sprint 17
Themes:
Requisitions - keep moving forward with new columns
Fulfillment - APIs to support the 'view orders' and 'manage POD' screens
Reference data - errors and enforcing rights
UI - see the UI section
Rollover Team ILL
Requisitions (template and improvements)
Bugs
Tickets
https://openlmis.atlassian.net/browse/OLMIS-924 Question about the formula - why n-1? Answer: addressed, should be n.
https://openlmis.atlassian.net/browse/OLMIS-218 Confirmation wanted: When skipping a requisition it does not participate in the calculations for next requisitions (eg. beginning balance)
https://openlmis.atlassian.net/browse/OLMIS-839 Would an endpoint on the backend that retrieves n last requisitions for the given facility, program and schedule make sense? We currently do not have one and it would simplify and speed up UI a lot
https://openlmis.atlassian.net/browse/OLMIS-1503 Needs clean up (blocks 1501/2)
Potentially
Need to add Ticket for capturing dates at each state change → to be displayed on View Requisitions, "approve" and convert to order screens.
Fulfillment
https://openlmis.atlassian.net/browse/OLMIS-1555 @Chongsun Ahn (Unlicensed) will fill out.
https://openlmis.atlassian.net/browse/OLMIS-1518 Should we check for status here? Eg. the new endpoint won't work for the already transferred orders
https://openlmis.atlassian.net/browse/OLMIS-1371 (blocked by https://openlmis.atlassian.net/browse/OLMIS-1512)
Any other tickets to support 'view orders screen'
UI
New functionality tickets
New columns
View/Calculate Total Requisition Cost
Comments
Product skipping and adding back previously skipped products
Vew orders
Tech Debt
Clean up translation strings. Let's define the end game for this for 3.0 https://openlmis.atlassian.net/browse/OLMIS-1252
Button styleguide
Sentence documentation (lowest priority and can be moved to next sprint) – Documentation should be written in 30 minutes this sprint
ILL work will be roll over:
https://openlmis.atlassian.net/browse/OLMIS-1072 https://openlmis.atlassian.net/browse/OLMIS-1514
Bugs
Ticket (in priority order)
https://openlmis.atlassian.net/browse/OLMIS-1525 (sub-task for Average Consumption)
https://openlmis.atlassian.net/browse/OLMIS-1084 (blocked by https://openlmis.atlassian.net/browse/OLMIS-1387)
https://openlmis.atlassian.net/browse/OLMIS-1549 (if the APIs are ready)
Stretch/Sprint 18
https://openlmis.atlassian.net/browse/OLMIS-1550 (if the APIs are ready)
Reference Data
https://openlmis.atlassian.net/browse/OLMIS-1558 Isn't this done? Also why should we enforce MANAGE_ROLES on rights endpoint?
Reference Data Stretch Goal:
https://openlmis.atlassian.net/browse/OLMIS-1444 (for Team ILL; pending Jake input)
Platform
https://openlmis.atlassian.net/browse/OLMIS-969 The ticket says no classes with ANY dependencies should be moved to shared library. How about classes with Jackson annotations? Eg. some DTOs
Add ticket to capture BI&A calls and effort to finalize the Product Model
Stretch goal (based on TOP/AYIC retrospective):
https://openlmis.atlassian.net/browse/OLMIS-1606
Stock Management
QA
https://openlmis.atlassian.net/browse/OLMIS-1014 Should creating a new user always require an e-mail? Should it be possible for an administrator to set user's password?