Goal: Focus on foundational work for 3.3 featureset feature set (local fulfillment, making an order (requisition lite), F&E, Reporting, mobile reference implementation)
...
(MUST)Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3618
roll over CCE tickets from Parrot Sprint 40 (everything in CCE was picked up from Backlog Grooming Sprint 40 (MUST)Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3244
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 pageThese features are going to be built incrementally, so we are adding functionality to fulfillment pages instead of trying to build the entire full feature set at once.
Prerequisite for other local fill ticketsJira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3607
Layer 1: (MUST)Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3613
Layer 2: (MUST)Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-36083607
Layer 3: (MUST)Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-36103608
Stock Management
Jira Legacy server System JIRA
...
...
serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-
...
3563
...
- (MUST)
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-
...
3485
...
- (MUST)
Jira Legacy server System JIRA
...
serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-
...
(MUST)3562 Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-
...
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.
(MUST)3295 Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3563 Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3485
(MUST)3027
Reference Data
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3295
(Brandon Bowersox-Johnson research the status quo–is order configurable right now?)Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3507 3537 - Placeholder for RTM tickets - outcome from service agreements
Nick Reid (Deactivated) should clean up this ticket before it goes into this sprintJira Legacy server System JIRA serverId448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3027
Reference Data
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-35372245 Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-22453135 Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2666
UI
...
- Team Parrot please pick 1-3 tickets from this epic to improve performance (keep in mind the most used/biggest impact should go first):
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3468 Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-31953623
UI
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3415
(ILLJira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3654
(MUST)3686
(ILL)Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3655 3468 Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-30803195 Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-33393415 Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-33263080
Stretch?Platform
(Team Parrot please steal this ticket from Team ILL board)Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-31083196 - Stretch:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-
3437
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3166
Team ILL
Team ILL
Goal: Tickets ready for SolDevelo next week (Fulfillment, RTM, Making an Order). Dependency: Mock data for reporting. GDHF prep work (integration PPT, integration POC JSON, etc, Tenly's presentation, kick-off meeting)
- MUST: GDHF integration lab session - Brandon Bowersox-Johnson to create a ticket for the JSON script for the October month. (Brandon will write ticket.)
- MUST: Create mock stock management datadata–Needs Discussion. Brandon Bowersox-Johnson Josh Zamor and MJ discussed using excel to build it out. Need . (Brandon will write ticket.)
- MUST: Mary Jo to create a ticket .
(Team ILL - should we work on the design for this? It is part of connecting Stock and Requisition)Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3099 - 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 for Digital Square Gap Analysis Ona/JSI/VR group kick off meeting prep
- Detailed presentation on vaccine features for AMP Benin (need by Dec. 12) (Tenly create a ticket) (Tenly will work on this presentation and get Review from Mary Jo)
DONE: Ticket to describe component releasing process (new) - add disclaimer about components not being fully regression tested (buyer beware) - Josh added a new paragraph in ReadTheDocs that says "Draft"
3167Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-
– Nikodem Graczewski3683 (
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 thisSam)
(Sam)Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3587 including the open questions in
(Brandon can collaborate with Sam)Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3505