Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2146
  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3583
  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3361
  •  

    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 

  •  

    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3108

  •  

    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-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 

    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3167
     – 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

  •  

    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3654
     (ILL)

  •  

    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3655
     (ILL)

  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3725
     (ILL)
  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2996
     (ILL)
  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3710
     (Rachel)
  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3711
     (Rachel)
  •  Local Fulfillment work on getting next round of work groomed:
    • Jira Legacy
      serverSystem JIRA
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3663
    • Jira Legacy
      serverSystem JIRA
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3610
    • Team ILL writing tickets about permissions/roles for Local Fulfillment
  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2814
    • This is a performance-y ticket, that might not be a great candidate for sprint 42 - but should happen