Release Candidates
Code Review
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-434 |
|---|
|
/ | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-644 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-671 |
|---|
|
- backend should already have been merged as part of other non-serial agreements
- should be clear to progress to QA
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-683 |
|---|
|
- Functionality complete
- Needs tests within components to complete
- Returned to
In Progress to complete
QA / UAT
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-680 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-569 |
|---|
|
Items at Risk / Spillover
- Open / Sprint Backlog
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-655 |
|---|
|
/ | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-427 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-688 |
|---|
|
- In Progress
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-692 |
|---|
|
- one test left to do, and then should be good to code review
- Mark is liaising
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-687 |
|---|
|
/ | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-690 |
|---|
|
- can use curl to get a kbart file and create a package
- cannot create searchable titleInstances yet
- would need to have a type of 'Electronic', which should fix it
- need to modify the ingest service to ensure the right publication dates are allocated
- then ready to move onto the UI (as defined in
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-688 |
|---|
|
)- can be simplified if needed to postpone prioritise update and focus on newvs new use cases
- Owen Stephens to confirm via subtasks
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-668 |
|---|
|
/ | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-684 |
|---|
|
- proof of concept went up for Owen this morning
- feedback has been very positive ("sick")
- searching is a good starting point with this
- next thing is the types of licenses to compare
- more work to do on collecting use cases, eg, internal notes across results
- filters essentially work
- waiting on text-contains backend, to be done as part of
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-704 |
|---|
|
- some better ui and cleanup needed for production
- parent issue is stable and now transitioned to
Open - do not have the ability to find licenses where terms are not set.
- some ui/designs mocked up
- question marks about how that could be implemented
- =null wouldn't work as nothing is null
- that part of it will be pushed back - Owen Stephens to create separate story for future rescheduling