Backlog Grooming Sprint 32
Goal
Two sprints left to complete CCE Service. Let's continue pushing ahead on Vaccines functionality. Sprint 33 is when we release 3.2.0 around August 30-31.
Team Parrot | Team ILL | Team Malawi |
|---|---|---|
Vaccines | Vaccine Tickets, UI Design and Tech Design | Bugs |
CCE | Spikes & Guidance | Configuration Report |
Connecting Stock and Requisitions |
| Performance |
New Admin Screen |
| Reporting Service (for contribution) |
Note: We are starting to include Malawi priorities on this backlog grooming in order to improve coordination and transparency between the teams. For example, the core team recently established a new system for Performance Testing, and now the Malawi team is going to build on that by adding performance tests to critical parts of the system, such as Convert to Order, that are key areas for the Malawi implementation.
Vaccines
CCE (MUST)
(Hey Pawel, these top 3 tickets are related/overlapping. Please read them all and divide up the work carefully between devs (or stagger the work)).
Connecting Stock Management and Requisitions (MUST)
QA & Testing
https://openlmis.atlassian.net/browse/OLMIS-2951 (Parrot - Joanna)
Reference UI
Filter control design change
Requisition
(none)
Fulfillment
Reference Data
https://openlmis.atlassian.net/browse/OLMIS-2853 (MUST) Admin screen
Stock Management
Auth
https://openlmis.atlassian.net/browse/OLMIS-2902 (cleaning up tech debt in Auth service; proposed by Team Parrot in Sprint 31)
Platform
https://openlmis.atlassian.net/browse/OLMIS-1652 (nice to have)
https://openlmis.atlassian.net/browse/OLMIS-2957 (ILL - josh)
Team Malawi
@Ben Leibert is identifying priorities and coordinating between teams
High priority bugs that will benefit the Malawi implementation to happen right away to be included in the 3.2.0 release at end of August
Potentially contribute to admin screens (such as the one listed above under Reference Data)
Reporting
https://openlmis.atlassian.net/browse/OLMIS-2838The MW likely introduced the issue, so we can fix it. (MUST)
https://openlmis.atlassian.net/browse/OLMIS-2841 @Josh Zamor (Deactivated) or @Ben Leibert I believe it's in your court to flesh out:
https://openlmis.atlassian.net/browse/OLMIS-2842 @Josh Zamor (Deactivated) or @Ben Leibert I believe it's in your court to flesh out:
Reference Data
https://openlmis.atlassian.net/browse/OLMIS-2912 (MUST)
this one may need more details in the ticket to move it from Roadmap to ToDo
https://openlmis.atlassian.net/browse/OLMIS-2716 (MUST) (The MW team reported this issue.)
https://openlmis.atlassian.net/browse/OLMIS-2713 (The MW team reported this issue.)
Requisition
https://openlmis.atlassian.net/browse/OLMIS-2680 (MUST)
for reference: Requisition initiate endpoint performance
https://openlmis.atlassian.net/browse/OLMIS-2681 (MUST)
Requisition object will need to understand the format laid out by reference data
Requisitions migrated to store a relevant permission string
https://openlmis.atlassian.net/browse/OLMIS-2429 (Low priority, but also low effort.)
https://openlmis.atlassian.net/browse/OLMIS-2908
Not a must for this sprint