Page Comparison

...

• Performance Test the 3.2.0 Snapshots with Malawi Data (Pending Discussion - Ben Leibert will raise this with developers - Core desires this info ASAP/Thursday)
  Details: Test what crashed the production server last month with the 3.2.0 component snapshots using the Malawi data set. If we do this quickly, we would have time to fix performance issues before 3.2.0. At the very least, this would prove to us whether 3.2.0 will fix the production performance issues that happened recently.
  Steps: Load MW environment up with Ref-Distro snapshots of components plus Malawi data. Run the performance tests. Josh also suggests we might modify the tests to do more concurrent users (in the YAML file).

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2680

   (It makes sense to have MW finish this.)

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2887

   (It makes sense to have MW finish this.)

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2716

   (Can probably be marked as Done.)

Reference Data

• Admin screen: 

  Jira Legacy
  server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2857

   (MUST) (perhaps the Malawi team)
• Admin screen: 

  Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2283

   
• performance:  improve facilities approved products p90

Reference UI

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2592

Requisition

• Next on performance needs some feedback from progress in Malawi on:  search, initiate, batch, data

Fulfillment

• performance:  have we done the measure of convert to order?

Reporting

• What are the next steps for Data connector?

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2762

   (perhaps Malawi can pick this up?)

Team ILL

• Add contract test demo data to get the checkAdminRight ticket committed (it's been reverted twice)

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2681

   (Performance Priority - Chongsun)

• Jira Legacy
  server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2939

   (Team ILL. Sam to edit this and add regression testing acceptance criteria)

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2920

   get some usability feedback on our UI patterns
  • table error patterns such as OLMIS-2797
  • table inline row adding OLMIS-2448
  • new filter pattern? OLMIS-2656
• Update New Country Implementation Recommendations with version 3

• Jira Legacy
  server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3015

• Jira Legacy
  server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3028

Nice to Have

Reference Data

• Admin screen: 

  Jira Legacy
  server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2857

   (perhaps the Malawi team)

Do Not Do (

...

reconsider for future sprints)

Team Malawi Past Rollovers

...