| Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|
| | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-498 |
|---|
|
| | BE: 1h FE: 1d - Split log retrieval end points (info, error, all)
- Add count for each end point per job
- Update accordians to use new endpoints
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-1467 |
|---|
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-1470 |
|---|
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-584 |
|---|
|
| | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-460 |
|---|
|
| | BE 1d FE 5d Potentially a single endpoint for both incoming and outgoing relationships (two separate properties) Or, having action endpoints per agreement (potentially more extensible) More investigation required. |
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-1467 |
|---|
|
| | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-459 |
|---|
|
| | BE FE Different objects are duplicated in different ways - sometimes you need a copy of the ID, rather than the same ID. Should be able to do UI separate to back-end, up to the point of saving. Back-end processing to follow. Cleanest way is to clone and save an agreement, and then treat it as an edit on the new agreement. TBD: ported values of Start & End Dates of Agreement Period FE needs to know format of what the BE will send/consume (object or string array likely - FE to decide). |
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-1467 |
|---|
|
| | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-497 |
|---|
|
|   | FE 1h Current period should be NULL, and has a key on the agreement. Needs to use that instead. |
| Common approach to handling these is required. | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-493 |
|---|
|
| | FE 2h (excluding tests)* Change to show a button tooltip that shows a user doesn't have permission. * Tests for permissions based stuff like this is not manageable. |
| Common approach to handling these is required. | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-495 |
|---|
|
| |
|
| Common approach to handling these is required. | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-496 |
|---|
|
| |
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-1669 |
|---|
|
| | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-283 |
|---|
|
|   | Still blocked by STCOM-576 |