Backlog Grooming Sprint 42

Owned by Mary Jo Kochendorfer (Deactivated)
Last updated: Jan 03, 2018 by Nikodem Graczewski (Unlicensed)
2 min read

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

Local Fulfillment

  • OLMIS-3614 - Getting issue details... STATUS  (MUST) Q
    • Josh Zamor needs to decide if Fulfillment will make a dependency on Stock Management
  • OLMIS-3382 - Getting issue details... STATUS  (MUST) Q

Creating an Order

The feature requirements are documented here /wiki/spaces/OP/pages/135823499.

Roll over from Sprint 41

Bugs

These are from the top of the backlog

  • OLMIS-3505 - Getting issue details... STATUS
    • Please propose solutions, and make sure there is alignment before starting to make changes
  • OLMIS-3688 - Getting issue details... STATUS
  • OLMIS-3537 - Getting issue details... STATUS  (Auth)
  • OLMIS-3492 - Getting issue details... STATUS
  • OLMIS-3541 - Getting issue details... STATUS
  • OLMIS-3527 - Getting issue details... STATUS
  • OLMIS-3513 - Getting issue details... STATUS  Q
  • OLMIS-3759 - Getting issue details... STATUS  Q

UI

DISC Visualization

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

  • OLMIS-3752 - Getting issue details... STATUS  (MUST)
  • OLMIS-3764 - Getting issue details... STATUS  (MUST) (Team ILL)
    • Sam Im (Deactivated):  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

  • OLMIS-2146 - Getting issue details... STATUS
  • OLMIS-3583 - Getting issue details... STATUS
  • OLMIS-3361 - Getting issue details... STATUS

  • 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 

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

  • OLMIS-3099 - Getting issue details... STATUS  (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  OLMIS-3167 - Getting issue details... STATUS  – Nikodem Graczewski (Unlicensed): we want you to re-start the discussion on the dev forum, ping Josh Zamor as needed, don't start coding anything yet for this

  • OLMIS-3654 - Getting issue details... STATUS  (ILL)

  • OLMIS-3655 - Getting issue details... STATUS  (ILL)

  • OLMIS-3725 - Getting issue details... STATUS  (ILL)
  • OLMIS-2996 - Getting issue details... STATUS  (ILL)
  • OLMIS-3710 - Getting issue details... STATUS  (Rachel)
  • OLMIS-3711 - Getting issue details... STATUS  (Rachel)
  • Local Fulfillment work on getting next round of work groomed:
    • OLMIS-3663 - Getting issue details... STATUS
    • OLMIS-3610 - Getting issue details... STATUS
    • Team ILL writing tickets about permissions/roles for Local Fulfillment
  • OLMIS-2814 - Getting issue details... STATUS
    • This is a performance-y ticket, that might not be a great candidate for sprint 42 - but should happen

OpenLMIS: the global initiative for powerful LMIS software