Scope #1, compute the indicators and make them available, is in progress.
Scope #2, transport the indicators to DHIS2, is scheduled for 3.6 but reduced in priority to give more space for reporting stack robustness (product ready). Design is proceeding: https://openlmis.atlassian.net/wiki/x/NIEyGw
Question: which DHIS2 version(s) should we support? (TZ is currently on 2.30, latest is 2.32).
Some notable restrictions on sending in batches, configuration using different endpoints, performance notes, etc
Recommendation is to use the broadcasts endpoint for 3.6 requirements, however for future requirements we might want to switch to flow_starts, however it should be noted that there'd configuration needed.
At the least would be knowing the flow id.
Could also include passing through a map of values to fill in a message template in the flow
Multiple checklists plugin in Jira
SolDevelo has developed an add-in to Jira, checklists inside tickets
Has been added to our OpenLMIS Jira
Just go try it in Jira
Action Items
Josh Zamor followup with Team Parrot on feature flags in performance improvements
Josh Zamor schedule a call on level setting on build failures (put out open invite), bring up notifications