Backlog Grooming Sprint 28
Objective: Improve performance, address critical bugs and start on stock management for vaccines, pushing requisitions to stock management.
Update as of 6/5: @Paweł Gesek please note the shift from CCE. We are putting a pause on CCE for the time being as we take a look into integrating with Logisitmo and its asset management functionality.
Releasing 3.1.2 (at end of this sprint on June 21)
@Paweł Gesek I would like your help with creating tickets for this sprint for releasing all the components (all except Ref-Distro). I'm not sure if you want individual tickets for each component OR just one ticket for a group of components. As before, part of the job is confirming the CHANGELOG is good, releasing (following docs.openlmis.org instructions), then updating SNAPSHOT for our next version we are working towards. We would also like your team to plan to release the Stock Management component plus the ones you had released last time. Team ILL will release Ref-Distro 3.1.2.
(@Paweł Gesek TBD)
Stock Management
The first three tickets are part of longer term approach of connecting the requisition service to stock management. Please review Connecting the Stock Service and Requisition Service for more context on the approach. We are only doing the first three because they shouldn't impact Malawi (or need a migration) since we will be releasing the 3.1.2 patch at the end of the sprint. Also, please watch the Stock Management Service Code Walkthrough video for an introduction to the stock management code base before starting work. The last two tickets are the start of new features for vaccines (2654 and 2663).
@Paweł Gesek to look at production ready and to clarify with the team to determine what is needed.
Working towards 1.0.0-SNAPSHOT
https://openlmis.atlassian.net/browse/OLMIS-2669 (MUST) Q: The UI approach here is not chosen yet.
https://openlmis.atlassian.net/browse/OLMIS-2671 (MUST) Q: Here as well we have two approaches outlined an open question for which one to use. @Josh Zamor (Deactivated), we need your input.
https://openlmis.atlassian.net/browse/OLMIS-2654 (MUST) Q: What will be the approach for configuring the VVM field availability? How should the VVM be stored (Josh's comment)?
Reference UI
Working towards 3.1.1
https://openlmis.atlassian.net/browse/OLMIS-2635 (ILL) (MUST - found in product testing)
https://openlmis.atlassian.net/browse/OLMIS-2637 (MUST - found in product testing) Q: need decisions on the approach
https://openlmis.atlassian.net/browse/OLMIS-2660 (ILL) (MUST)
NR: There is a more general bug underneath this — unknown and unselected options are both shown (resulting in that weird bubble)
https://openlmis.atlassian.net/browse/OLMIS-2626
Nice to Have:https://openlmis.atlassian.net/browse/OLMIS-2443
Apply to user screen
Apply to login screen
Requisition
Working on 4.0.0 because we are committing work on performance/payload that breaks past API consumers by removing unneeded fields!
Reserve for Malawi: Performance: 2017-06-07 Meeting notes
@Ben Leibert to write up a ticket on requisition DTO and where it is used by the UI Edit: I ended up creating MW-304, MW-305, and MW-306. Because their target audience is clearly a developer external to the core team, I didn't ultimately include them in the OLMIS project. I'd be happy to clone and move them, however, if you still prefer.
https://openlmis.atlassian.net/browse/OLMIS-2641 (Needs discussion about approach; Josh posted 3 strategies)
https://openlmis.atlassian.net/browse/OLMIS-2638 (ILL) (MUST - found in product testing)
https://openlmis.atlassian.net/browse/OLMIS-2596 (MUST) Q: Could use more reproduction info
https://openlmis.atlassian.net/browse/OLMIS-2636 (MUST - found in product testing) Q: does this still occur? I cannot repro
https://openlmis.atlassian.net/browse/OLMIS-2567 (MUST - found in product testing) Q: are we opting for option C?
https://openlmis.atlassian.net/browse/OLMIS-2543 Q: How we want to deal with notifications? i.e. on initialize page
https://openlmis.atlassian.net/browse/OLMIS-2612
Nice to Have bugs:https://openlmis.atlassian.net/browse/OLMIS-2429 (@Josh Zamor (Deactivated) UI now has character limit, should we dead this?)
Reference Data
Will be working towards 6.0.2
https://openlmis.atlassian.net/browse/OLMIS-2664 (MUST - this is the copy of Malawi bug - MW-301 FYI: @Ben Leibert)
https://openlmis.atlassian.net/browse/OLMIS-2280
Nice to Have
Fulfillment
Platform
https://openlmis.atlassian.net/browse/OLMIS-1498 (MUST) - I've changed this to just implement the thing, we already did the spec on Confluence.
Stretch:
Reporting
https://openlmis.atlassian.net/browse/OLMIS-2668 (Reserved for Malawi)
We'll hold off on finishing: https://openlmis.atlassian.net/browse/OLMIS-2250
Team ILL
Still to be created (and ping Mary Jo or Brandon to add to the sprint as soon as you create):
@Rachel Powers (Deactivated) create a ticket Creating tickets for stock management
@Rachel Powers (Deactivated)create a ticket for Senegal workshop prep
@Josh Zamor (Deactivated) to create tickets from tech committee (for himself)
ODK time needs new ticket
Malawi - performance and reporting
Already in sprint 28:
UI Design : https://openlmis.atlassian.net/browse/OLMIS-2553
https://openlmis.atlassian.net/browse/OLMIS-2645 (@Tenly Snow (Deactivated) and @Sam Im (Deactivated))
https://openlmis.atlassian.net/browse/OLMIS-2665 (need to complete the change by end of June)
CCE
Working towards 1.0.0-beta. New component to support the feature set needed for implementers to manage their Cold Chain Equipment (Catalog, inventory, update temperature, RTM, and notifications).
Functional Documentation and Background : A. Manage CCE Catalog, tickets in https://openlmis.atlassian.net/browse/OLMIS-2624
Functional Documentation and Background: B. Manage CCE Inventory, tickets in https://openlmis.atlassian.net/browse/OLMIS-2625
Open Question: How does Reference Data factors into CCE? Or not? Please clarify this in the tickets/documentation.