Goal: Focus on foundational work for 3.3 featureset (local fulfillment, making an order (requisition lite), F&E, Reporting, mobile reference implementation)
CCE
- OLMIS-3618 - Getting issue details... STATUS
- OLMIS-3244 - Getting issue details... STATUS
- roll over CCE tickets from Parrot Sprint 40 (everything in CCE was picked up from Backlog Grooming Sprint 40)
Fulfillment
/wiki/spaces/OP/pages/88670474. The approach suggested for building out the new fulfillment screen is to approach it in layers. Layers will each introduce new functionality which builds out the whole page.
- OLMIS-3607 - Getting issue details... STATUS
- Prerequisite for other local fill tickets OLMIS-3613 - Getting issue details... STATUS
- Layer 1: OLMIS-3608 - Getting issue details... STATUS
- Layer 2: OLMIS-3610 - Getting issue details... STATUS
- Layer 3: OLMIS-3614 - Getting issue details... STATUS
- Layer 4: OLMIS-3620 - Getting issue details... STATUS
- Layer 5: OLMIS-3622 - Getting issue details... STATUS
- OLMIS-3382 - Getting issue details... STATUS Can be done at any point after Layer 1
Rachel Powers (Deactivated) to flesh out these tickets with mockups and also bring in relevant AC from early local fill tickets (640, 910, 529)
Rachel Powers (Deactivated) it would be great if you could start slotting the first tickets for work. Chongsun Ahn (Unlicensed), should we start with a hello world? Are the backend changes needed? Rights/roles?
Stock Mgmt
- OLMIS-3563 - Getting issue details... STATUS
- OLMIS-3485 - Getting issue details... STATUS
- OLMIS-3295 - Getting issue details... STATUS
- OLMIS-3507 - Getting issue details... STATUS (Brandon Bowersox-Johnson research the status quo–is order configurable right now?)
- OLMIS-3027 - Getting issue details... STATUS Nick Reid (Deactivated) should clean up this ticket before it goes into this sprint
Reference Data
- OLMIS-3537 - Getting issue details... STATUS
- OLMIS-2245 - Getting issue details... STATUS
- OLMIS-3135 - Getting issue details... STATUS (RTM tickets - outcome from service agreements Josh Zamor to add more details in ticket)
- OLMIS-2666 - Getting issue details... STATUS
UI
Question: What is the priority of improving the batch requisitions screen?
- OLMIS-3657 - Getting issue details... STATUS This is Malawi's top priotity. If someone on the Core team with more UI experience can take it on, that would free Sebastian to devote most (maybe all) of his time to the Core team.
- OLMIS-3468 - Getting issue details... STATUS
- OLMIS-3195 - Getting issue details... STATUS
- OLMIS-3415 - Getting issue details... STATUS
- OLMIS-3654 - Getting issue details... STATUS (ILL)
- OLMIS-3655 - Getting issue details... STATUS (ILL)
- OLMIS-3080 - Getting issue details... STATUS
- OLMIS-3339 - Getting issue details... STATUS
- OLMIS-3326 - Getting issue details... STATUS
Stretch?
- OLMIS-3108 - Getting issue details... STATUS
- OLMIS-2146 - Getting issue details... STATUS
- OLMIS-3166 - Getting issue details... STATUS
Team ILL
- MUST: Create mock stock management data. Brandon Bowersox-Johnson Josh Zamor and MJ discussed using excel to build it out. Need to create a ticket.
- OLMIS-3099 - Getting issue details... STATUS (Team ILL - should we work on the design for this? It is part of connecting Stock and Requisition)
- Consider working on the new plan for 360-day calendar issues and the 30/31 Stock-Out-Day data entry validations. See longer-term plan for how to address this in a different way has been mapped out for after v3.2.1:
Adjusted Consumption calculations and 360-day calendar (Mary Jo Kochendorfer (Deactivated) how high or low of a priority is this?) - Create a CHANGELOG file for Reporting Service (we have none! https://github.com/OpenLMIS/openlmis-report)
- Brandon pinged Nikodem about OLMIS-3167 - Getting issue details... STATUS – Nikodem Graczewski (Unlicensed): we want you to re-start the discussion on the dev forum, ping Josh Zamor as needed, don't start coding anything yet for this
-
OLMIS-3587
-
Getting issue details...
STATUS
(Sam)
- including the open questions in OLMIS-3505 - Getting issue details... STATUS (Brandon can collaborate with Sam)