Backlog Grooming Sprint 29

Notes for MJ

• ask about regression and contract testing 

Objective: New things - tying together requisitions & stock management and potentially start CCE work (pending update from Governance committee).

Please make sure all tickets in this sprint are marked FIXED VERSION: 3.1.3

Stock Management

Working towards stockmanagement-1.0.0-SNAPSHOT. NOT BEING INCLUDED IN 3.1.2

We would like to move forward with more new stock management features for vaccines.

• OLMIS-2710 - Getting issue details... STATUS  (Follow-up step in VVMs FYI Mary Jo Kochendorfer (Deactivated) and Rachel Powers (Deactivated))
• OLMIS-2693 - Getting issue details... STATUS
• OLMIS-2639 - Getting issue details... STATUS
• OLMIS-2711 - Getting issue details... STATUS
  • Q: in ticket
  • Ticket will be broken up into smaller sections
    • Backend logic
    •  Print out
    • Reusable UI component
• OLMIS-2729 - Getting issue details... STATUS

Nice to have

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

Requisition

Working on requisition-4.0.1

• OLMIS-2612 - Getting issue details... STATUS  (This is Fulfillment as well)
• OLMIS-2193 - Getting issue details... STATUS
• OLMIS-2753 - Getting issue details... STATUS
• OLMIS-2429 - Getting issue details... STATUS
• OLMIS-2715 - Getting issue details... STATUS

• Sam Im (Deactivated) add bugs (added 2729, 2715, deaded 2717 on 6/20... still looking for more).

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  OLMIS-2624 - Getting issue details... STATUS

These new features should be prioritized for this sprint

• OLMIS-2752 - Getting issue details... STATUS (MUST)

• OLMIS-2615 - Getting issue details... STATUS (MUST)
  
  
• OLMIS-2609 - Getting issue details... STATUS

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

Reference UI

• Nick Reid (Deactivated) will find ticket about documenting UI branding
• OLMIS-2659 - Getting issue details... STATUS  (This needs to get reproduced)
• OLMIS-2602 - Getting issue details... STATUS
• OLMIS-2443 - Getting issue details... STATUS
  
  • Apply to user screen
  • Apply to login screen
• (Larger issue here is a dynamic navigation/breadcrumb items)
  • Nick Reid (Deactivated) to find ticket

Stretch:

• OLMIS-2655 - Getting issue details... STATUS
• OLMIS-2661 - Getting issue details... STATUS  (Team ILL)

Reference Data

Working towards: 6.0.3.  

• OLMIS-2709 - Getting issue details... STATUS  
  • (Perhaps a database issue–need to discuss how we solve it. This is a performance issue with facilities? endpoint that kills the Admin → Users → Edit screen. Added by Ben and Brandon for consideration. ALSO, after we make this fix, we need to roll a release of the RefData API and UI components so Malawi can pick up this "hot fix", not waiting for ref-distro 3.1.3. Paweł Gesek please let us know if this hot fix idea makes sense to you and the team.)
  • Q: I am not clear what are we supposed to do here, solve the performance issue or try finding the 'hanging' issue (possible that hanging is the performance issue). Facilities are used by a select dropdown - we probably will have to extend the select mechanism to support backend pagination in order to have an improvement here.
    • Title is slightly incorrect — the chrome browser used to load this ends up crashing because of performance
    • Josh said that the server does take about 40 seconds, he would like to see RAML
    • Total payload size is about 2mb (which is HUGE)
    • Nick Reid (Deactivated) will make a related ticket to have the UI lazy load this
• OLMIS-2600 - Getting issue details... STATUS
• OLMIS-2277 - Getting issue details... STATUS
  • Q: Apparently we didn't want to have this before?
  • Q (from NR): Do we want to add acceptance criteria to this that the UI should do validation before submission, or treat that separately). — Please do at the same time.
• OLMIS-2411 - Getting issue details... STATUS
• OLMIS-2647 - Getting issue details... STATUS
• OLMIS-2238 - Getting issue details... STATUS
  • Q: Is sorting by the username ok here?
    • Sort by username by default
    • Make sure the page is preserved
• OLMIS-2446 - Getting issue details... STATUS  
  • Q: is breadcrumbs out of scope? A: Yes

Fulfillment

• OLMIS-2724 - Getting issue details... STATUS
• OLMIS-2726 - Getting issue details... STATUS

Reporting

Nice to Have: 

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

Platform

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

Stretch:

• OLMIS-2147 - Getting issue details... STATUS (Josh Zamor to move to todo after AC check?) (is this or  OLMIS-2611 - Getting issue details... STATUS a dupe of OLMIS-1689 - Getting issue details... STATUS i.e. could we dead the latter)
• OLMIS-2627 - Getting issue details... STATUS  (Paweł Gesek Please read this ticket and let us know if you think it's feasible and how you would approach it; it would likely need guidance or involvement from you)
• OLMIS-1329 - Getting issue details... STATUS (Josh Zamor to check AC)
• OLMIS-1509 - Getting issue details... STATUS (Josh Zamor to update AC - ODK developers would find this useful)

General/Testing/QA

• OLMIS-2721 - Getting issue details... STATUS
• OLMIS-2722 - Getting issue details... STATUS
• OLMIS-2748 - Getting issue details... STATUS  (Team ILL)