| 1 | View existing Supervisory Nodes | As an admin I want to view existing Supervisory Nodes so that I can see the system's approval hierarchy. Acceptance Criteria: - View list of all Supervisory Nodes in the system and details associated: SN code, Assigned Facility, Parent & Child relationships, Requisition Groups assigned
| | Must Have | | 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-2280 |
|---|
|
- Open bug:
| 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-2411 |
|---|
|
|
| 2 | Create new Supervisory Nodes | As an admin I want to create new Supervisory Nodes so that I can support business needs for new approval points. Acceptance Criteria: - Ability to create new Supervisory Nodes
- Assign new Supervisory Nodes an associated facility
- Assign new Supervisory Nodes to user through User Roles
|
|
| | 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-2282 |
|---|
|
|
| 3 | Edit existing Supervisory Nodes | Currently, right assignments are changed when a user's role assignments are changed, which is fine for direct and fulfillment role assignments. However, for supervisory structural changes, right assignments need to be refreshed in order for them to stay in sync with the supervisory structure. Some scenarios: - When a requisition group is added to/removed from a supervisory node
- When a supervisory node is added to/removed from another supervisory node
|
|
|
|