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 | MWOLMIS-2322583 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | MWOLMIS-1592509 |
---|
|
(may be fixed with the 3.1 drop OLMIS-2476)- 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 | MWOLMIS-1862573 |
---|
|
(Seemingly related to MW-159, above)- NR: This should be fixed in OLMIS-1693 Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key |
---|
|
MW142 Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | MW-222 |
---|
|
(Looks fairly easy to address) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key |
---|
|
MW168
Reference UI
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-19251889 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-24441925 |
---|
|
(Q: Isn't this moving us to the rainbow style?) A: Yes, maybe just adding icons(Team ILL)
Stretch:
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2447249 |
---|
|
(NR: OLMIS-1354 & OLMIS-2510 might intersect with this, but doing some work across all services here would be good) - 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- |
---|
|
1189 (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- |
---|
|
2509 (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- |
---|
|
249 (Angular strap has hard coded string.... need other library)Sonar- Show unit test coverage
- Show UI file size (pre-compression) display library size vs code-base size
UI file size when compressed to track growth between builds) (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-2315 |
---|
|
(NR: discussing this with UI team – going to "dead" this ticket once a decision is made)- Make UI build process faster....
Requisition
Will be working towards XX
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-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 | OLMIS-2530 |
---|
|
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-2531 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2543 |
---|
|
(Brandon Bowersox-1133Johnson, 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
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
...
Reference Data
Will be working towards 6.0.1
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-2536 |
---|
|
This endpoint should filter the facilities (this is a dependency for MW-170) 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-2494 |
---|
|
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 |
---|
|
...
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2385 |
---|
|
(Q: Do we want front-end validation? A: Yes)
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-2292 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
|
...
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
...
(very small) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
...
(very small) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
...
Stretch:
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-2552 |
---|
|
(likely shouldn't pick this up, if we did, Reference Data would be working on v7.0.0 - the next major release)Fulfillment
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2551 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2532 |
---|
|
Platform
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 |
---|
|
...
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:
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 |
---|
|
...
Reporting
Roll-over from last sprint.
Issues Discovered During Malawi UAT
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-2585 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
...
...
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
|
...
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2587 |
---|
|
(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 Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2588 |
---|
|
(Q: What is the status of this ticket?) A: Will be dead after OLMIS-2476 Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
...
Reporting
Team ILL
...
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2578 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2581 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2580 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2582 |
---|
|
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:
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2590 |
---|
|
Performance Testing of key endpoints (find the ticket for it)
Refactor so we can accept the batch approve page in requisitions