ERM Sprint 95
Sprint Goal / Focus
Sprint Schedule
Sprint: 95
Release: Honeysuckle
Quarter: 2020 Q3
Start Monday 27 July, 2pm UK
Finish Friday 14 Aug, 12pm UK
Navigation
Sprint Planning
- not in sprint
or @ - in sprint
Brought Forward
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
For Release -> Done, with spinoffs.
| |||
For Release -> Done | |||
@Owen Stephens | Merged for QA.
| ||
https://folio-org.atlassian.net/browse/ERM-943 / https://folio-org.atlassian.net/browse/ERM-944 / https://folio-org.atlassian.net/browse/ERM-945 | @Claudia Malzer | Done: TODO:
Specification is sufficient for now.
| |
@Aditya matukumalli | Works alongside https://folio-org.atlassian.net/browse/ERM-1003 to deliver https://folio-org.atlassian.net/browse/UXPROD-2440.
| ||
@Aditya matukumalli | Back-end has been done for this. Merged into ERM-1000 as a subtask. | ||
@Aditya matukumalli | Similar code area as ERM-1000, but not part of that functionality. Adi to pick up to avoid code conflict. | ||
@Ethan Freestone | 1d | ||
@Ethan Freestone | 1d | ||
|
Sprint Focus
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
@Aditya matukumalli | To pick this off before ERM-1000 | ||
@Owen Stephens | In QA | ||
@Peter Böhm | In Progress | ||
@Peter Böhm | Follows on from ERM-510. Some placeholders have been put in for data to be logged. These need to be replaced to make more useful for users, now that ERM-510 is complete and output can be observed.
| ||
Steve |
| ||
Ethan / Steve |
| ||
Peter / Steve | To follow ERM-1010. | ||
Steve |
|
Brought In
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
| @Aditya matukumalli | Comparison reports are not loading quickly enough, eg partials.
| |
| @Ethan Freestone | Duplicate coverage array | |
|
| Code is async based on promises. So fetch doesn't support linear process. Could make this use of endpoints tricky. Relates to https://folio-org.atlassian.net/browse/CHAL-208. Ian to discuss with Steve. If progressable potentially with Ethan. | |
| @Ethan Freestone | Progressable. Need to work out mod-config | |
| @Ethan Freestone | Investigation piece. If it cannot be fixed, remove the sort options from the UI. | |
| @Ethan Freestone | Done and done. | |
| @Claudia Malzer | Ready to progress | |
| @Gill Osguthorpe | To be fixed in stripes. Then requires a review of ERM apps for replacement calendar widget, specifically where date picker is used within card component. | |
| @Claudia Malzer |
| |
| @Claudia Malzer |
| |
| @Claudia Malzer |
| |
| @Claudia Malzer | Change agreement search to unlink Organisation and Content Provider filters. Maybe affected by https://folio-project.slack.com/archives/CAYCU07SN/p1595238491191800 | |
| @Claudia Malzer | Simple change to extend matched fields for Search | |
| @Claudia Malzer | Simple change to extend matched fields for Search | |
@Gill Osguthorpe | Should be able to progress a solution (if not a perfect or FOLIO wide solution) | ||
| https://folio-org.atlassian.net/browse/ERM-1048 / https://folio-org.atlassian.net/browse/ERM-1047 Could do with technical review and assess approach. Best to leave until II and OS return | ||
UX Improvements |
|
|
|
Comparisons Feedback |
|
|
|
| Potentially transfer to Ethan ... | ||
| @Claudia Malzer | Compare with ERM-815. Check backend can sort as part, but not expecting backend changes to be made as part of this. | |
| @Aditya matukumalli | To pick up as alongside of ERM-1000 | |
| @Ethan Freestone |
| |
| @Ethan Freestone |
|