| Requirement | Description | Epic | Notes |
|---|
Each request status should be linked to the work task that is has been assigned to | Jira |
|---|
| showSummary | false |
|---|
| server | jira.ihtsdotools.org JIRA |
|---|
| serverId | b202d822-d767-33be-b234-fec5accd5d8c |
|---|
| key | CRS-23 |
|---|
|
| When a work task status changes, this status should be reflected in the request JIRA issue | Request Status | This is likely to be done by the orchestration service during authoring. When an authoring task changes status, it would check with the traceability DB and change the status of the relevant request tickets |
Each batch of requests should provide a quick view as to the status| Jira |
|---|
| showSummary | false |
|---|
| server | jira.ihtsdotools.org JIRA |
|---|
| serverId | b202d822-d767-33be-b234-fec5accd5d8c |
|---|
| key | CRS-22 |
|---|
|
| When viewing a batch, there should be a quick summary view of the number of requests in the batch and their relevant status | Request Status | |
Users are notified when a request status changes| Jira |
|---|
| showSummary | false |
|---|
| server | jira.ihtsdotools.org JIRA |
|---|
| serverId | b202d822-d767-33be-b234-fec5accd5d8c |
|---|
| key | CRS-24 |
|---|
|
| When a request status changes as above, then the relevant requesting user should receive a notification email | Notifications | |