ERM Sprint 87
Sprint Goal / Focus
Sprint Schedule
- Sprint: 87
- Release: Goldenrod
- Quarter: 2020 Q4
- Start Monday 6 Apr, 2pm UK
- Finish Friday 17 Apr, 12pm UK
Sprint Capacity
Team Availability: Schedule | Calendar
Notes / Exceptions:
- Gill Osguthorpe off sprint week 1, returning 14 Apr
- NA: Good Friday and Easter Monday
- 13 Apr: No mid-sprint planning
Lead Roles:
- Front End Code Review: md331 (Deactivated)
- Back End Code Review: steve.osguthorpe
- QA: Owen Stephens
QA Environment: folio-testing
Navigation
Sprint Planning
- not in sprint
or @ - in sprint
Backend unblockers (steve.osguthorpe ):
- - ERM-800Getting issue details... STATUS
- - ERM-748Getting issue details... STATUS / - ERM-777Getting issue details... STATUS
- - ERM-814Getting issue details... STATUS
Sprint Candidates
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
Aditya matukumalli | Does not include duplicating amendments. Expect user to select options in a similar way as with duplicating licenses. TODO:
Backend Priority: after Delete Agreement/License. | ||
TODO:
Agreements is higher priority than Licenses. | |||
All backend for now. Plus wireframes. Not likely to start until Sprint Week 2. Typical use case includes storing metadata for use in json export (csv and tsv would be more of an issue). Custom properties need to be discrete from other custom properties. Frontend likely to be buried like amendments, making is much less discoverable. Potentially opens the desire for searchable agreement lines / entitlements. Any functionality driven by custom properties as this would be very process expensive - making it highly improbable. Use cases linked on feature: https://docs.google.com/document/d/11RxHJZXY5YuPiEQNPQsjlO92_N_s4pLjGniotUly8fs/edit?pli=1
Still need to address the issue of agreement lines having reached its usability limit. | |||
Backend - 5 minutes. Trivial backend model to replicate | |||
Brought Forward
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
PR raised - ready for code review? | |||
Preventing a delete on an agreement/license doesn't prevent the deletion of related objects. | |||
Preventing a delete on an agreement/license doesn't prevent the deletion of related objects. | |||
| |||
Some preliminary work done on ERM-793. New branch set up on mod-agreements with trusted tag Needs to check it is applied in the right places | |||
Add embargo info to JSON and KBART export formats.
Will be ready to progress for when Peter returns on Wednesday. |