<5 mins | Introductions | |
|
| Previous Actions | |
|
|
|
|
|
| WIP Update | Release CandidatesCode Review: QA / UAT For ReleaseItems at Risk / SpilloverIn Progress Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1544 |
---|
|
- Previously
- refactored agreement filters
- showing all filters and new tags filter working
- old tags not working in switch to functional structure
currently debuggingReady for code review
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1564 |
---|
|
- Backend integration tests in progress
- Should take around 30-40 minutes
- Otherwise development done
- Update
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1547 |
---|
| Previouslyreset use state may be effectiveform object should yield the object reference needed - Need to refactor whole component to functional and then use relevant hook
- Good examplar to model from - should only be a couple of days, but unlikely to be ready for review or QA this sprint.
- Tricky bit may be componentDidMount - Ethan to point to alternative
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1580 |
---|
|
- Need to abstract some of implementation to make it less massive
- Won't be fully optimised in this iteration, but should be a good enough drag and drop model for future implementers
- No good drag and drop test library currently available
- Key press tests for accessibility do work
- Aim is to develop a reusable component for any field array
- End-to-end demo should be doable on Thursday
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1581 |
---|
|
- basically done
- needs to be extended to amendments as well
- due for code review todayreturned from code review to implement as a function
- see 1537
Sprint BacklogNeeds Elaboration Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1540 |
---|
| / Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1541 |
---|
| / Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1542 |
---|
| / Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1543 |
---|
|
- No technical architect input ... Ethan to chase
- Q: Should vendor / primary institution be migrated?
- Needs test data for migration handling
Closed Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1579 |
---|
|
| |
<10 mins | AOB | New Issues Added to sprint NA Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1537 |
---|
|
- reopened to resolve in comparable way to ERM-1581
Not added to sprint Organisation Roles Issues: Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1540 |
---|
| / Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1541 |
---|
| / Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1542 |
---|
| / Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1543 |
---|
|
Previously - REQ: change current setup to support
- multiple organisations with multiple roles for an agreement or license
- one primary organisation per license or agreement (pattern as per contact address)
- UNKNOWNS:
- impact on filtering by org(s)/role(s)
- migration
- TASK TBC: new domain class on SubscriptionAgreement to support role-note pairs
- Remove exclusive vendor restriction
- PLAN:
- Ethan: determine data model and class changes (solicit feedback from Ian/Steve)
- Owen: add migration scenarios to issue
- Claudia: review updated information and define work breakdown required
Permissions - Some discussion about adding descriptions into package,json.
- No technical reason not to add them.
- Therefore stories to follow
| |
|
|
|
|