Page Comparison

Notes for MJ

...

Rachel is working on creating nice to have tickets for notifications and VVM to issue and/or receive, new tickets tbd

Requisition

Working on requisition-4.0.1

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

   (Pending outcome of performance testing to see if Convert to Order is still a critical speed issue.)

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

   (This is Fulfillment as well)

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

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

  • (Nick Reid (Deactivated) some UI discussion there to figure out with Mary Jo Kochendorfer (Deactivated) so we can get started on this)
  • This work could be combined with OLMIS-2711

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

• 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-2715

...

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

   (Perhaps a database issue–need to discuss how we solve it. This is a performance issue with facilities? endpoint that kills the Admin → Users → Edit screen. Added by Ben and Brandon for consideration. ALSO, after we make this fix, we need to roll a release of the RefData API and UI components so Malawi can pick up this "hot fix", not waiting for ref-distro 3.1.3. Paweł Gesek please let us know if this hot fix idea makes sense to you and the team.)
  Q: I am not clear what are we supposed to do here, solve the performance issue or try finding the 'hanging' issue (possible that hanging is the performance issue). Facilities are used by a select dropdown - we probably will have to extend the select mechanism to support backend pagination in order to have an improvement here.

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

• 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-2277

  Q: Aparrently we didn't want to have this before?

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

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

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

  Q: Is sorting by the username ok here?

Fulfillment

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

...