/
Backlog Grooming Sprint 42

Backlog Grooming Sprint 42

Jan 03, 2018

Goal: Priority goes to vaccine features (fulfillment, creating an order, and reporting).  

Local Fulfillment

https://openlmis.atlassian.net/browse/OLMIS-3614 (MUST) Q

  • @... needs to decide if Fulfillment will make a dependency on Stock Management

Creating an Order

The feature requirements are documented here Create an Order.

https://openlmis.atlassian.net/browse/OLMIS-3782 Q

Roll over from Sprint 41

Bugs

These are from the top of the backlog

https://openlmis.atlassian.net/browse/OLMIS-3505

  • Please propose solutions, and make sure there is alignment before starting to make changes

UI

DISC Visualization

Data oriented to unblock Team Ona on visualization for the DISC indicators

https://openlmis.atlassian.net/browse/OLMIS-3764 (MUST) (Team ILL)

  • @...:  do we have users that have the stock manager role for the two facilities in the AC of this ticket? - we want to demo putting stock card data in, and showing it in reporting

Testing

Team ILL

Ticket for work on ideal use case for OpenHIE sub committee preparation (Josh throw out the architect's ideal process, circulate it to OpenLMIS community, meeting is 15th)Later?
not yet sure of deadline Received word from Libya MOH that they are presenting OpenLMIS as a solution and want to use OpenSRP as a mobile client for OpenMRS backend 
https://openlmis.atlassian.net/browse/OLMIS-3099 (Team ILL - should we work on the design for this? It is part of connecting Stock and Requisition)
Consider working on the new plan for 360-day calendar issues and the 30/31 Stock-Out-Day data entry validations. See longer-term plan for how to address this in a different way has been mapped out for after v3.2.1:Adjusted Consumption calculations and 360-day calendar (@Mary Jo Kochendorfer (Deactivated) how high or low of a priority is this?)
Create a CHANGELOG file for Reporting Service (we have none! https://github.com/OpenLMIS/openlmis-report)
Brandon pinged Nikodem about https://openlmis.atlassian.net/browse/OLMIS-3167 – @Nikodem Graczewski (Unlicensed): we want you to re-start the discussion on the dev forum, ping @Josh Zamor (Deactivated) as needed, don't start coding anything yet for this

Local Fulfillment work on getting next round of work groomed:

https://openlmis.atlassian.net/browse/OLMIS-2814

  • This is a performance-y ticket, that might not be a great candidate for sprint 42 - but should happen

Comments

OpenLMIS: the global initiative for powerful LMIS software