Page Comparison

...

• Features

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4842

     (Team Mind the Gap - continuing from work started before 3.6)

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5626

     (JSI)
    • Scope still needs to be clarified further and determined if we will use our extension approach to collecting program data. The following is some background on the previously discussed approaches to implementing program data. We will need to figure out if we have time and expertise to do this with the ^ feature
      • Program Data Capture

      • Jira Legacy
        server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-549

  • Notifications (MtG) the following pages and epics should be reviewed and the 3.6 scope still needs to be defined.
    • Requisition - Customizable notification messages 
    • Notifications - Push Reminders

    • Jira Legacy
      server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1094

• Interface
  • DHIS2 - 

    Jira Legacy
    server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5443

  • Interface - Google Analytics
• Reports
  
  • Reporting - Data pump for R&R and SM - we originally discussed doing this but don't see this on the list of epics

    • Jira Legacy
      server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5492

       Josh is currently working on the pumps

...