Versions Compared

Key

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

 

Attendees

Discussion

Gap Feature Groupings: Gap Feature Groupings

Roadmap Epics: https://openlmis.atlassian.net/issues/?filter=20570

Potential Goals

...

Gap Teams

  • Features

    • Jira Legacy
      serverSystem JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-
    5443
    • 4842
       (Team Mind the Gap - continuing from work started before 3.6)
    • Jira Legacy
      serverSystem JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-5626
       (Team Mind the Gap)
      • Scope still needs to be clarified further and determined if we will use our program

Action Items

  •  Type your task here, using "@" to assign to a user and "//" to select a due date


Goals for Team Parrot

  • Architecture
    • Release faster (this needs scoping)
    • Demo data (needs scoping)
    • Performance

Goals for external JSI

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

Considerations with Scheduling

  • Ona is the only team which can (currently) build on reporting
    • We need to train the other teams soon though
  • DHIS2 is going to be handled within the Reporting stack
  • OLMIS-5626 scope needs to be further defined and JSI is a key stakeholder
  • Data pump work should be done by micro-service/Java teams

Action Items