Page Comparison

NOTE: Malawi soft launch early July

Malawi

Discuss picking up bugs logged from Malawi. Objective: to continue addressing critical bugs (performance and major UI issues)

Reference UI

NR: These will make working with the UI easier

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

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

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

   - NR: Is this a dupe of OLMIS-2328

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

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

   - NR: This should be fixed in OLMIS-1693

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

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

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

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

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

  (Team ILL)

Stretch:

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

   - NR: Angular strap has hard coded string, might need another library

Requisition

Working on 3.1.5-SNAPSHOT (the incoming changes due to performance issue will most likely result in version 4.0.0 being the case)

Brandon Bowersox-Johnson to create a ticket to (coordination and fixes on both the UI and endpoints and even other things) to either reduce requests and decreased payload. Brandon Bowersox-Johnson were you able to create this ticket, is it either 2565, 66, 84, or 33?

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

   (Which Malawi bugs does this address? A: Requisition load time)

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

   (Q: Solution for this will probably be the same as for

  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-2584

  ) (Which Malawi bugs does this address? A: Requisition view/approve/convert to order)
  Make sure to reference the related Malawi bugs 

  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 MW-232

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

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

   (Q: proposed solution in comment)
  (In addition to what Łukasz included in his daily report on timeouts - we have increased the maximum execution time, but this is a temporary workaround. The requests already take too long time for certain things (especially reports since they usually require a lot of data). The root reason is requisition related endpoints returning a lot of unnecessary data - I've created a ticket for this in core (OLMIS-2533) but if it becomes problematic quickly we may need to fix it ourselves and contribute this to the core product - Sebastian 5/17)
  • Remove previous requisition history
  • Do BA work to decide what is actually needed (where/when) 
  • FYI, the Malawi logged bugs 

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

    ,

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

    ,

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

    ,

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

    , MW-171.

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

   This endpoint should filter the facilities (this is a dependency for MW-170)

  2522

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

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

...

• OLMIS-2530

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

   (Q: Isn't this moving us to the rainbow style?)

  2193

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

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

   (NR: OLMIS-1354 & OLMIS-2510 might intersect with this, but doing some work across all services here would be good) Brandon Bowersox-Johnson, does this need further directions?)

• OLMIS-1133 (NR: Can we make a ticket to gather requirements/design/socialize this issue?)

Reference Data

Will be working towards 6.0.1

...

...

...

...

...

Requisition

Will be working towards XXQ: Do we want front-end validation? A: Yes)

...

...

...

...

...

Reference Data

Will be working towards 6.0.1

Stretch:

...

Fulfillment

Platform

...

Stretch Goal: 

Stock Management: Change it from Hibernate to Flyway before our next/non-beta release (or move this to Grooming 28?? Team ILL)

Stretch:

...

Reporting

Roll-over from last sprint.

Issues Discovered During Malawi UAT

...

...

...

...

Q: As far as we remember this was the desired behavior. Do we want to clear the table when changing requisition type/any input value?) A: Waiting for OLMIS-2554

...

2476

...

...

...

Fulfillment

• insert

...

Team ILL

...

...

...

...

...

...

...

...

...

...

Contract testing dev-wide short presentation (see a few ideas on retrospective)

15-minute design meetings after stand-up (do not need a ticket for this; but we will pilot this idea during Sprint 27)

Stretch goals:

...

...

Reporting

Josh - would we aim to finish up the tickets in progress?

...

Performance Testing of key endpoints (find the ticket for it)

Refactor so we can accept the batch approve page in requisitions