Goal: Focus on foundational work for 3.3 featureset feature set (local fulfillment, making an order (requisition lite), F&E, Reporting, mobile reference implementation)
...
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 |
---|
|
(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 |
---|
|
roll over CCE tickets from Parrot Sprint 40 (everything in CCE was picked up from Backlog Grooming Sprint 40 (MUST)
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.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3607 |
---|
|
Prerequisite for other local fill tickets 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 1: (MUST) Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-36083607 |
---|
|
Layer 2: (MUST) Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-36103608 |
---|
|
Layer 3: 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-3614 |
---|
|
Layer 4: (MUST)
Stock Management
...
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
...
...
- (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- |
---|
|
...
...
| 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
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)
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 |
---|
|
Jira Legacy |
---|
server | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3507 |
---|
|
(Brandon Bowersox-Johnson research the status quo–is order configurable right now? (MUST) Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3027 |
---|
|
Nick Reid (Deactivated) should clean up this ticket before it goes into this sprintMUST)
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-3537 |
---|
|
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-2245 |
---|
|
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-3135 |
---|
|
(RTM tickets - outcome from service agreements Josh Zamor to add more details in ticket) 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
Question: What is the priority of improving the batch requisitions screen?
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3657 |
---|
|
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.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-34683623 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3195 |
---|
|
UI
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3415 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3654 |
---|
|
(ILL (MUST) Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-36553468 |
---|
|
(ILL) 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
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-31083196 |
---|
|
(Team Parrot please steal this ticket from Team ILL board)- Stretch:
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
2146 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 .
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3099 |
---|
|
(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
Jira Legacy |
---|
server | System JIRAfor 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"
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- |
---|
|
3167 – 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 thisSam)
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 |
---|
|
(Sam)