Backlog Grooming Sprint 26
Last sprint before 3.1 release. Key features to be demonstrated are related to stock management workflows (conduct a physical inventory, make an adjustment, record an issue/receive), tracking lots and new administration screens. The following tickets are focusing on addressing bugs and stabalizing the requisition service.
Reference UI
Goals: Consistency
Needs Design Work (Expect implementation tickets to fall out of these tickets, not sure if they will make it to 3.1)
https://openlmis.atlassian.net/browse/OLMIS-2428 and https://openlmis.atlassian.net/browse/OLMIS-2275 MUST
https://openlmis.atlassian.net/browse/OLMIS-2224 (Team ILL) In progress
Stretch Goal:
Requisition
Will be working towards 3.1.3-SNAPSHOT. Because requisition-3.1.2 was released in ref-distro-3.0.2.
https://openlmis.atlassian.net/browse/OLMIS-2491 Try to reproduce
https://openlmis.atlassian.net/browse/OLMIS-2480 Try to reproduce
https://openlmis.atlassian.net/browse/OLMIS-2351 (very small)
Stretch Goal:
Reference Data
Will be working towards 5.1.0-SNAPSHOT. Because referencedata-5.0.0 is planned to be released in ref-distro-3.0.2. Improvements such as 2357 make this a Minor bump to 5.1.0, not a patch 5.0.1. Reference Data is working on 6.0.0 due to final changes to accomplish OLMIS-1696.
https://openlmis.atlassian.net/browse/OLMIS-2371 MUST(is split out by https://openlmis.atlassian.net/browse/OLMIS-2413)
Stretch
Fulfillment
https://openlmis.atlassian.net/browse/OLMIS-2484 (needs to be reproduced) MUST
https://openlmis.atlassian.net/browse/OLMIS-2243 (Should be checked to see if still issue) MUST
Platform
Reporting
Team ILL
Discuss how we will keep these moving forward:
Should Program Data PoC proceed without Chongsun?
Should ad-hoc Reporting proceed?
Improve workflow so that fixing bugs results in a new automated test
https://openlmis.atlassian.net/browse/OLMIS-1751 (@Josh Zamor (Deactivated) perhaps the design of this is a topic to discuss while you are in Gdynia?)