Cold Chain Equipment Movements
Target release | 3.13 |
|---|---|
Epic | |
Document status | DRAFT |
Document owner | |
Technical Lead |
Goals/Scope
Allow users with the appropriate privileges to move cold chain equipment from one facility to another using the OpenLMIS UI.
Historical information about the equipment should include the facility that it was at when the event occurred - out of scope for 3.13 release, should be considered in the future releases
Background
This request originated in the SELV instance in Mozambique. Forum post was created to discuss this feature.
Assumptions
User Stories
Personas: Relevant user personas for this feature are the <INSERT PERSONA'S> (see personas)
Title | User Story | Label | Importance | Notes | JIRA Ticket | |
|---|---|---|---|---|---|---|
| 1 |
|
|
|
|
|
|
| 2 |
|
|
|
|
|
|
Diagrams/Process
User navigates to CCE Management -> CCE Inventory
User selects the facility and program to search for CCE associated with it
User for CCE that he wants to transfer and clicks on "View" button
User with an appropriate rights searches can see "Transfer" button and click on it
Modal pops up with fields
“Facility” - select field
"Program" - select field - this should be a list of programs that user has ability to work with
"Year of Installation/Commission” - text field
User can choose the facility to transfer and enter the new year installed
Once user clicks on "Save" button, fields' values are updated
Facility is updated
Program is updated
Installed Year is updated
Facility update does not have any further implications somewhere
Dependencies
Description | Link |
|---|---|
Open Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome | Status | |
|---|---|---|---|
| 1 | Josh: Who is the user than can move equipment? Does it need any review from another user? |
| Open |
| 2 | Hubert: Which facilities should be displayed in select field? Should only facilities for the chosen program be displayed? | It should be reduced to facilities that the user is supervising, not to the program. User can also change the program. | Open |
| 3 | Nikola: Should we add migration for role so user who have "Edit CCE" also have "Transfer CCE"? | Wes: No, it's a new role and should not be the same as edit cce. | Open |
Out of Scope
History of CCE - both, the history of status updates and the history of movements
Work Plan
# | Task | Story Points | Notes/Questions | Jira Ticket |
|---|---|---|---|---|
1 | Add "Transfer CCE" right | 2 | Add this right to Supervision role type | |
2 | Update Facility and Year Installed fields | 5 | Add new endpoint for CCE transfer and make sure that everything works fine after update of those fields | |
3 | Create modal for CCE Transfer | 3 | Create modal and add "Transfer" button next to "Update Status" button | |
4 | Add tests for CCE Movements | 2 |
|