2019-02-15 Team Lead Meeting Notes

Feb 15, 2019

Attendees

@Sebastian Brudziński @Clay Crosby (Unlicensed) @Craig Appl (Unlicensed) @Ashraf

Discussion Point

• https://openlmis.atlassian.net/browse/OLMIS-5449

  • There's probably no any work planned to not have the reports hardcoded at this point

  • If we keep the hardcoded approach, implementations would need to overwrite their own UI file to include their own reports

  • Alternative: one iframe for the whole superset, instead of having them one per report, and then define roles per dashboard in Superset

  • We will follow up on the Backlog grooming for team parrot (25 feb) with the LOE and options that we have

  • Superset exposes APIs for retrieving the available dashboards

•  Reminders:

  • Start your sprints, update the sprint goal, and the grooming page

  • Backlog Grooming Sprint 119

Mind the Gap (Sam):

 -

Parrot (Sebastian):

• Need more discussion and estimates before we can take on https://openlmis.atlassian.net/browse/OLMIS-5449

• Work on supply lines performance improvements and perf tests for it

• Work on fixing broken builds

• One more functional tests planned

Ona (Clay/Craig):

• Janette is working on FHIR - doing research and writing tickets to scope down the work

• Persisting the reporting stack after restart - completed (one ticket may be in review)

• Clay will write configuration guide / building charts

• Risk: there's no FHIR resource to store stock value - Janette is looking into that as a part of the research

JSI (Ashraf):

• Discussed kitting with Josh, but unfortunately this spawned even more questions; will discuss this further with Wes

• Action items / follow-ups are tracked in 2019-02-14 Kitting Meeting notes

• Ashraf and Elias are looking whether they can start work on the reference data upload UI - converting the tool to microservice + looking whether uploading all resources work

• Risk: there are a lot of complex edge cases to consider with kitting, like unpacking kits and products having different quantities that are defined in stock mgmt

• We will see whether the edge cases will be making it into 3.6 (might be re-prioritized to include them post 3.6)

Action Items