Backlog Grooming Sprint 27
Objective: to continue addressing critical bugs (performance and major UI issues)
Reference UI
NR: These will make working with the UI easier
- - OLMIS-2509Getting issue details... STATUS - NR: Is this a dupe of OLMIS-2328
- - OLMIS-2439Getting issue details... STATUS
- - OLMIS-2573Getting issue details... STATUS - NR: This should be fixed in OLMIS-1693
- - OLMIS-2572Getting issue details... STATUS
- - OLMIS-1889Getting issue details... STATUS
- - OLMIS-1925Getting issue details... STATUS (Team ILL)
Stretch:
- - OLMIS-249Getting issue details... STATUS - 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?
- OLMIS-2565Getting issue details... STATUS (Which Malawi bugs does this address? A: Requisition load time)
- OLMIS-2566Getting issue details... STATUS (Q: Solution for this will probably be the same as for - OLMIS-2584Getting issue details... STATUS ) (Which Malawi bugs does this address? A: Requisition view/approve/convert to order)
Make sure to reference the related Malawi bugs - MW-232Getting issue details... STATUS- - OLMIS-2584Getting issue details... STATUS
-
-
OLMIS-2533Getting issue details...
STATUS
(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) - - OLMIS-2522Getting issue details... STATUS
- - OLMIS-2514Getting issue details... STATUS
- - OLMIS-2530Getting issue details... STATUS
- - OLMIS-2193Getting issue details... STATUS
- - OLMIS-2531Getting issue details... STATUS
- - OLMIS-2543Getting issue details... STATUS (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
- OLMIS-2574Getting issue details... STATUS
- OLMIS-2536Getting issue details... STATUS This endpoint should filter the facilities (this is a dependency for MW-170)
- OLMIS-2494Getting issue details... STATUS
- OLMIS-2277Getting issue details... STATUS (Q: Do we want front-end validation? A: Yes)
- OLMIS-2292Getting issue details... STATUS
- OLMIS-2385Getting issue details... STATUS (very small)
- OLMIS-2384Getting issue details... STATUS (very small)
- OLMIS-2495Getting issue details... STATUS
Stretch:
- OLMIS-2552Getting issue details... STATUS (likely shouldn't pick this up, if we did, Reference Data would be working on v7.0.0 - the next major release)
Fulfillment
- OLMIS-2551Getting issue details... STATUS
- OLMIS-2532Getting issue details... STATUS
Platform
- OLMIS-2147Getting issue details... STATUS
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:
- OLMIS-2574Getting issue details... STATUS
Reporting
Roll-over from last sprint.
Issues Discovered During Malawi UAT
- OLMIS-2584Getting issue details... STATUS
- OLMIS-2585Getting issue details... STATUS
- OLMIS-2586Getting issue details... STATUS
- OLMIS-2587Getting issue details... STATUS (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
- OLMIS-2588Getting issue details... STATUS (Q: What is the status of this ticket?) A: Will be dead after OLMIS-2476
- OLMIS-2548Getting issue details... STATUS
Team ILL
- OLMIS-2578Getting issue details... STATUS
- OLMIS-2581Getting issue details... STATUS
- OLMIS-2580Getting issue details... STATUS
- OLMIS-2582Getting issue details... STATUS
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:
- OLMIS-2590Getting issue details... STATUS
Performance Testing of key endpoints (find the ticket for it)
Refactor so we can accept the batch approve page in requisitions
OpenLMIS: the global initiative for powerful LMIS software