| Priority | Item | Who | Notes |
|---|
| | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2340 |
|---|
|
| | |
| | Permission validation | | - Either user role determines which program I can create stock event or my home facility support program determines? Or both. View source, destination, reason we have the validation rule to check whether my home facility supports such program;
- The event creation permission for adjustment/receive/issue are shared by the same role - stock management. Is it correct? Meaning, anyone who can make adjustment will also be allowed to create receive/issue stock event.
No need to do.
|
| | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-1862 |
|---|
|
| | - Json blob, do we need to do it?
|
| | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-1696 |
|---|
|
| | - Efforts are required by dependency confilct
|
| | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2451 |
|---|
|
| | |
| | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2496 |
|---|
|
| | |
| | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-706 |
|---|
|
| | - Integrate with stock card template configuration
|
| | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2441 |
|---|
|
| | - Source/destination assignment
|
| Remove physical inventory draft | | - When the draft is incorrect, there is no workaround for user.
|
| How to handle existing reference data change | | - Deactivate products/facilities/programs in the reference data then how should stock management service handle that?
- Remove active products from the approved product list in the reference data then how should stock management service handle it?
|
| Demo data for UAT |
|
|
| Notification feature |
|
|
| Configuration document: e.g. including setting up reason, source, destination |
|
|
| Re-organize the wiki page of each feature: adjustment, physical inventory ect. |
|
|