ERM Sprint 99
Sprint Goal / Focus
- Honeysuckle Release Readiness
Sprint Schedule
- Sprint: 99
- Release: Honeysuckle
- Quarter: 2020 Q4
- Start Monday 5 Oct, 2pm UK
- Finish Friday 17 Oct, 12pm UK
Navigation
Sprint Planning
- not in sprint
or @ - in sprint
Brought Forward
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
PR removed: see comment on issue KBART export dynamically creates header, which it probably shouldn't. Some concern about grabbing private fields. Decision is to make this static. Needs to be done for Honeysuckle, so this week, so reassigning to Ethan in Peter's absence. Estimate: <1d | |||
Mechanism of translating one URL to another is solid. Implementation details are broadly understood.
|
Sprint Focus
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
Initial suggestion is a PUT problem as name is different in item resource object / owner name. May be resolved by using owner name rather than id. Initial investigation suggests something funky is going on. Requires further backend investigation. | |||
- ERM-1158Getting issue details... STATUS | Owen Stephens to add test cases. Options:
FE: 0.5d | ||
| Not to be merged to master for Honeysuckle. Sort issue identified through ERM-1141 Backend should support the sort. On retrieval, toggle the sort option retrieved from the manifest. Impact is to fetch records from backend each time, which is performance. Better alternative is to implement SearchAndSort sort. TODO: Remove frontend sorting (ERM-1161)
| ||
Remove previous sort options FE: 0.5d | |||
Add Load More to 'eResources covered by the agreement' MCL as this is regularly going to exceed 100 items. FE: 0.5d | |||
Progressed to QA | |||
Progressed to Code Review | |||
Claudia Malzer | Potentially simple styling or property change, depending on how it is rendered. | ||
For QA to verify whether this has been fixed in the meantime, either by the change attempted, or perhaps Grails 4 upgrade. | |||
Errors are hardcoded in the frontend. Multiple error scenarios handled by the same error. TODO for this scenario:
FE: <0.25d | |||
May be affected by sort options issue that has arisen from ERM-1141. May need backend sorting. Update: coverage and sort changes to not be progressed. | |||
No queries. | |||
Will need to be re-enabled locally. | |||
Ethan Freestone | No queries | ||
Owen Stephens | To investigate whether multiple sort options resolves this. | ||
- ERM-1079Getting issue details... STATUS | May need a more elegant solution, but underlying it would still need two permissions. | ||
May have been resolved by titleInstance publication changes. Verification needed that this is still an issue. May only applies to resolver created titleInstances. | |||
Peter Böhm to take ERM-1157. | Not to be merged to master for Honeysuckle. BE: 0.5d FE: 1w + tests Backend:
Frontend: New framework tests haven't been set up on CI yet. | ||
Any interface versions can be wrapped as optional, but subject to - FOLIO-2808Getting issue details... STATUS being resolved.
| |||
Release Tickets: ERM-1165 to ERM-1174 | Adi / Ethan | Sprint Week 2
|
Brought In
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
. | |||
To be rolled back to avoid issues with ERM-1160. Whether to reinstate is subject to review of how MCLs are used in agreements. | |||
Removed
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
Removed in 2020-10-07 ERM Weekly Delivery Update. |