Backlog Grooming Sprint 30
Goals: Continue building new features in Stock Management and Cold Chain Equipment. Major bugs. Performance. New UI component.
CCE
@Paweł Gesek Could you review the scope for A. Manage CCE Catalog and B. Manage CCE Inventory and let me know if you think it is better for the team to focus on one epic (Catalog) before moving to the next (Inventory). Or should we first create both domain models?
https://openlmis.atlassian.net/browse/OLMIS-2604 (MUST) - UI was split into separate tickets
Nice to have
https://openlmis.atlassian.net/browse/OLMIS-2618 (if we don't want to start on the inventory we could continue to build out catalog tickets)
Q: @Paweł Gesek ILL would like to try making showcase videos for the above CCE tickets (OLMIS-2609 & 2618) – please comment if you agree.
Stock Management
Finish all parts of https://openlmis.atlassian.net/browse/OLMIS-2711 (in current sprint but has lots of sub-tasks)
@Brandon Bowersox-Johnson to work on next tickets for connecting Req and SM based on Connecting Stock Management and Requisition Services - Team ILL
https://openlmis.atlassian.net/browse/OLMIS-2790 (needs investigation)
Q: Maybe do a showcase video on OLMIS-2711 once it is finished.
Requisition
Fulfillment
https://openlmis.atlassian.net/browse/OLMIS-2781
(based on discussion in PR #4 — @Paweł Gesek has reviewed the issues there and has a suggestion for how we move forward: his suggestion is to remove the GET /api/orders endpoint entirely. This "get all orders" endpoint is not used by the UI or anyone as far as we know. Instead everyone will use the /api/orders/search endpoint to find a specific set of orders returning a list of order UUIDs. Pawel also believes the GET /api/orders is not in v2, it was only created in v3 but never used. @Josh Zamor (Deactivated) do you agree?
@Paweł Gesek, please see latests guidance in OLMIS-2781
Reference UI
https://openlmis.atlassian.net/browse/OLMIS-2655 Q: Should we add this to an existing screen? If yes, which one?
https://openlmis.atlassian.net/browse/OLMIS-2738 (needs to be reproduced)
https://openlmis.atlassian.net/browse/OLMIS-2714 (Needs to be reproduced — also needs review to see if general bug and 'global' approach can be taken)
https://openlmis.atlassian.net/browse/OLMIS-2803
The remaining work here is centering the modal (and actually all modals)
There is a discussion about how center we want these modals to be (generally off center looks right)
Ideally the modals would adjust based on the screen height
Reference Data
https://openlmis.atlassian.net/browse/OLMIS-2716 (Need additional feedback in comments from @Josh Zamor (Deactivated) before working on this.)
https://openlmis.atlassian.net/browse/OLMIS-2787
@Paweł Gesek does it make sense for @Lucyna Laska (Unlicensed) to do this before she leaves? Would other devs use this?
Reports
Platform
https://openlmis.atlassian.net/browse/OLMIS-2812 - (ILL) Josh
https://openlmis.atlassian.net/browse/OLMIS-2813 - (ILL) Josh
@Paweł Gesek, please ask the leads to do this → upgrade Gradle and tooling versions (see https://groups.google.com/forum/#!topic/openlmis-dev/2LpkxEk5vFM). If everything goes to hell, please let us know so we can discuss.
Malawi Contributions
Team ILL and @Ben Leibert and @Sebastian Brudziński to figure out how to get the following features back into core.
Report Service
Performance work
Batch approval
blocked by refactor work in the requisition service
UI could be structured as separate service
UI - Login page
Loading modal ticket
UI - Select2
MW-268 & MW-274
UI - Login Service
Configurable currency
Cleaner version of clearing user data
@Josh Zamor (Deactivated) notes.
Add ticket(s) for Next Step on Performance Benchmarking and performance fixes. Can we take the MW team results from OLMIS-2701 and turn it into a wiki page with a standard suite of tests we can periodically benchmark against? Mary Jo created a Non-Functional wiki page where we should clarify our non-functionality performance goals/standards. Also, MW team has specifically identified MW-366 and MW-367 to fix. (Team ILL)
https://openlmis.atlassian.net/browse/OLMIS-2147 (@Josh Zamor (Deactivated) to move to todo after AC check?) (is this or https://openlmis.atlassian.net/browse/OLMIS-2611 a dupe of https://openlmis.atlassian.net/browse/OLMIS-1689 i.e. could we dead the latter)
https://openlmis.atlassian.net/browse/OLMIS-2627 (@Paweł Gesek Please read this ticket and let us know if you think it's feasible and how you would approach it; it would likely need guidance or involvement from you)
https://openlmis.atlassian.net/browse/OLMIS-1329 (@Josh Zamor (Deactivated) to check AC)
https://openlmis.atlassian.net/browse/OLMIS-1509 (@Josh Zamor (Deactivated) to update AC - ODK developers would find this useful)