Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 53 Next »

Goal: Continue to work towards feature goals for 3.3 (vaccine stock based requisition, Receiving/POD, Local Fulfillment, etc.), make progress on Administration screens and critical needs for implementers.

Dates:  -  

3 sprints left (1 sprint is for testing) until 3.3 release on  

Vaccine Stock Based Requisitions

Fulfillment

  • OLMIS-4077 - Getting issue details... STATUS
  • OLMIS-3826 - Getting issue details... STATUS
  • OLMIS-2734 - Getting issue details... STATUS
    • Fulfillment current Integration Test approach slows developers down
  • OLMIS-4119 - Getting issue details... STATUS

Receiving and Proof Of Delivery:

Sebastian Brudziński and Nikodem Graczewski (Unlicensed) are leading this section. Please review and confirm these are still the next up and if you need any review by Team ILL. 

Emergency Requisitions

Sebastian Brudziński to update this section with the smaller tickets.

Ordering Quantities

Ideal Product Model

Administration

UI


Reporting

Mary Jo Kochendorfer (Deactivated) Clay Crosby (Unlicensed) — Discuss what work needs to go into the next sprint

Clay Crosby (Unlicensed)'s comments: I think after our discussion on the last call, ticket 3922 is no longer considered that high priority due to the value of the other things the team needs to work on versus the value that we'd get out of having more demo data (which would just make visualizations look better). Mary Jo Kochendorfer (Deactivated) noted that she would be able to talk through the limitations of the amount of demo data we have when giving a demo.

I don't think we need to make that adjustment to the API mentioned in ticket 4018 for the Gavi demo. It would certainly be easier from a performance API, but I don't believe we need to have that done for the demo. We would need it done before the system goes live into PRD, along with moving to a websub model for pushing data to NiFi. Flagging Josh Zamor and Craig Appl (Unlicensed) for their input on this ticket as well.  

Stock Reason Tagging (only pick up if there's space)

Supports stock based requisitions in finding quantities such as total consumed, total losses and adj, received, etc.  Supports reporting in finding the reasons which contribute in a flexible/configurable manner.  We still don't know if we can get what this unblocks in scope, so please do not pick-up if not able. Part of epic OLMIS-4131 - Getting issue details... STATUS

RTM Integration with CCE and Fulfillment

Scope for 3.3,  OLMIS-4106 - Getting issue details... STATUS  

Bugs

  • OLMIS-3982 - Getting issue details... STATUS
  • OLMIS-3513 - Getting issue details... STATUS
  • OLMIS-3759 - Getting issue details... STATUS  (quick win)
  • OLMIS-3974 - Getting issue details... STATUS  (needs to be done for 3.3)

Questions on bugs

  • OLMIS-3883 - Getting issue details... STATUS  (Nikodem Graczewski (Unlicensed) and Nick Reid (Deactivated) could you let me know how we want to address this)
    • Nick would like to take this opportunity to do a refactor of the navigation component (so we can have more consistent navigation throughout the UI)
  • OLMIS-3893 - Getting issue details... STATUS  Can we address this in 3958? What is the status Brandon?
  • OLMIS-4004 - Getting issue details... STATUS  Do we think this is demo data or something else?
  • OLMIS-3894 - Getting issue details... STATUS  Brandon did you look into this bug?

Quick Wins

type key summary assignee reporter priority status resolution created updated due
Refresh


Team ILL

  • No labels

OpenLMIS: the global initiative for powerful LMIS software