Objective: to continue addressing critical bugs (performance and major UI issues)
NR: These will make working with the UI easier
Stretch:
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?
(Which Malawi bugs does this address? A: Requisition load time)
(Q: Solution for this will probably be the same as for ) (Which Malawi bugs does this address? A: Requisition view/approve/convert to order)
Make sure to reference the related Malawi bugs
OLMIS-1133 (NR: Can we make a ticket to gather requirements/design/socialize this issue?)
Will be working towards 6.0.1
This endpoint should filter the facilities (this is a dependency for MW-170)
(Q: Do we want front-end validation? A: Yes)
(very small)
(very small)
Stretch:
(likely shouldn't pick this up, if we did, Reference Data would be working on v7.0.0 - the next major release)
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:
Roll-over from last sprint.
(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
(Q: What is the status of this ticket?) A: Will be dead after OLMIS-2476
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:
Performance Testing of key endpoints (find the ticket for it)
Refactor so we can accept the batch approve page in requisitions