| Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-3861 |
---|
|
| Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2053 |
---|
|
| | - Current State
- focus issue - resolved
- slowness issues - separate, so shouldn't stop progress on this
- TODO
- Development Estimate
|
| Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2836 |
---|
|
| | PARK until MCL pagination is resolved - Current State
- Failure when deleting one agreement line when there are more than one
- TODO
- Add new agreement line rather than delete any previously existing one
- ie, avoid changing original test when extending it
- Development Estimate:
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-4413 |
---|
|
| Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2983 |
---|
|
| | - Current State
- using parse/deparse (except for has/hasNot)
- TODO
- changes to supp props and checklist
- requires an extender to handle has/hasNot:
- stub a new Jira issue to cover this - assign to Ethan
- add context note in comment with link to issue
- link as related issue
- implement deparser
- Development Estimate: Wed
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-3885 |
---|
|
| Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-3018 |
---|
|
| | - Current State
- Reviewed and run through to scenarios 3.x satisfactorily
- Added new exception case
- Some blanks / unknown in testing scenarios - no known mechanism for recreating in live environment
- TODO
- Handle sibling TI identifier wrangling scenarios
- Upgrade testing, ie, QA vs existing data or vs existing resolver service, will have to be done alongside dev testing because of backend resource requirements
- add workflow diagram to issue
- Development Estimate: end of week
|
| Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-3024 |
---|
|
|
| In Code Review |
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-3890 |
---|
|
| Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2992 |
---|
|
|
| In Code Review |
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-4436 |
---|
|
| Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-3010 |
---|
|
|
| In Code Review |
| Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-3038 |
---|
|
|
| In Code Review |
| Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-3040 |
---|
|
|
| In Code Review |