Backlog Grooming Sprint 33

Note: we removed CCE tickets from the Parrot sprint 22 from the sprint and first priorities since we must finish the other tickets before wrapping up the CCE features. Team Malawi has full sprints and will not be taking on any global work.

Please make sure all tickets are marked with 3.2.

Release 3.2.0

• Testing?
• Releasing Components
• Releasing ref-distro
• OLMIS-3020 - Getting issue details... STATUS  (Team ILL)
• Video demos of new functionality
• Blog post

Connecting Stock Management & Requisitions

• OLMIS-2671 - Getting issue details... STATUS  (MUST)
• OLMIS-2834 - Getting issue details... STATUS  (MUST)
• OLMIS-3023 - Getting issue details... STATUS  (MUST)

Bugs

Prioritized in descending order (not including the roll overs). Please let Mary Jo Kochendorfer (Deactivated) know if you disagree or believe something should be a higher priority. All bugs below are a MUST unless otherwise noted.

• OLMIS-2908 - Getting issue details... STATUS  

• OLMIS-2724 - Getting issue details... STATUS  (can team Malawi work on this one?)
• OLMIS-2726 - Getting issue details... STATUS  (can team Malawi work on this one?)
• OLMIS-3017 - Getting issue details... STATUS

• OLMIS-2867 - Getting issue details... STATUS  

• OLMIS-2898 - Getting issue details... STATUS ?
• OLMIS-3019 - Getting issue details... STATUS
• OLMIS-2714 - Getting issue details... STATUS
• OLMIS-2903 - Getting issue details... STATUS  (nice to have, but not necessary)

Nice to Have (More Vaccines Scope)

CCE

• OLMIS-2872 - Getting issue details... STATUS  
• OLMIS-2893 - Getting issue details... STATUS  
• OLMIS-2995 - Getting issue details... STATUS
• OLMIS-2913 - Getting issue details... STATUS
• performance: should start measuring here

 Stock Management for Vaccines

• OLMIS-2732 - Getting issue details... STATUS

Team Malawi

• Performance Test the 3.2.0 Snapshots with Malawi Data (Pending Discussion - Ben Leibert will raise this with developers - Core desires this info ASAP/Thursday)
  Details: Test what crashed the production server last month with the 3.2.0 component snapshots using the Malawi data set. If we do this quickly, we would have time to fix performance issues before 3.2.0. At the very least, this would prove to us whether 3.2.0 will fix the production performance issues that happened recently.
  Steps: Load MW environment up with Ref-Distro snapshots of components plus Malawi data. Run the performance tests. Josh also suggests we might modify the tests to do more concurrent users (in the YAML file).
• OLMIS-2680 - Getting issue details... STATUS  (It makes sense to have MW finish this.)
• OLMIS-2887 - Getting issue details... STATUS  (It makes sense to have MW finish this.)
• OLMIS-2716 - Getting issue details... STATUS  (Can probably be marked as Done.)

Team ILL

• OLMIS-3030 - Getting issue details... STATUS
• OLMIS-2681 - Getting issue details... STATUS  (Performance Priority - Chongsun)
• OLMIS-2832 - Getting issue details... STATUS  (MUST / Team ILL)
• OLMIS-2939 - Getting issue details... STATUS  (Team ILL. Sam to edit this and add regression testing acceptance criteria)
• OLMIS-3032 - Getting issue details... STATUS  (Tenly)
• OLMIS-3015 - Getting issue details... STATUS  (Tenly)
• OLMIS-3028 - Getting issue details... STATUS  (Tenly)

Nice to Have

Reference Data

• Admin screen:  OLMIS-2857 - Getting issue details... STATUS  (perhaps the Malawi team)

Do Not Do (reconsider for future sprints)

Team Malawi Past Rollovers

• OLMIS-2841 - Getting issue details... STATUS  (Somewhat on hold; probably won't make in into 3.2)
• OLMIS-2842 - Getting issue details... STATUS  (Somewhat on hold; probably won't make in into 3.2)
• OLMIS-2758 - Getting issue details... STATUS  (Seems relatively low priority for MW.)
• OLMIS-2429 - Getting issue details... STATUS  (Relatively low priority) 
• OLMIS-2912 - Getting issue details... STATUS  (Nice to have. However, it seems convert to order work should take precident if possible.)