ERM Sprint 87

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 Goal / Focus Sprint Capacity Review sprint candidates  Agree technical approach / define key implementation tasks Finalise estimates / costings Confirm sprint scope Confirm first actions

 

 

Sprint Planning  

 - not in sprint

 or @ - in sprint 

 

Backend unblockers (steve.osguthorpe ):

Sprint Candidates

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/UXPROD-2347

https://folio-org.atlassian.net/browse/ERM-814

Aditya matukumalli

Does not include duplicating amendments. Expect user to select options in a similar way as with duplicating licenses.

TODO:

  • Apply Cloneable to license (as added to Agreement) - copy the controller action from agreements

  • Exclude Amendments

  • Assume same frontend shape

  • Note: do not commit to master until backend is completed

Backend Priority: after Delete Agreement/License.

https://folio-org.atlassian.net/browse/UXPROD-2267

https://folio-org.atlassian.net/browse/ERM-827 / https://folio-org.atlassian.net/browse/ERM-828

Claudia Malzer

TODO: 

  • Add alternative name as a collection an object with single string field

  • Similar to multiple OrgRoles as an array

  • Backend first, then frontend

  • Owen to add screenshots

  • FE with ReactFinalForm array (such as with Contacts)

Agreements is higher priority than Licenses.

https://folio-org.atlassian.net/browse/UXPROD-2352

https://folio-org.atlassian.net/browse/ERM-829 

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

Owen Stephensto revisit options with usergroup

Still need to address the issue of agreement lines having reached its usability limit. 

https://folio-org.atlassian.net/browse/UXPROD-2352

https://folio-org.atlassian.net/browse/ERM-779

md331 (Deactivated)

Backend - 5 minutes.

Trivial backend model to replicate

 

https://folio-org.atlassian.net/browse/ERM-694

md331 (Deactivated)

 

Brought Forward

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/UXPROD-2124

https://folio-org.atlassian.net/browse/ERM-547

Peter Böhm

PR raised - ready for code review?

https://folio-org.atlassian.net/browse/UXPROD-2346

https://folio-org.atlassian.net/browse/ERM-748

steve.osguthorpe

Preventing a delete on an agreement/license doesn't prevent the deletion of related objects.

https://folio-org.atlassian.net/browse/UXPROD-2345

https://folio-org.atlassian.net/browse/ERM-777

steve.osguthorpe

Preventing a delete on an agreement/license doesn't prevent the deletion of related objects.

https://folio-org.atlassian.net/browse/UXPROD-2344

https://folio-org.atlassian.net/browse/ERM-805

Claudia Malzer

 

https://folio-org.atlassian.net/browse/UXPROD-2124

https://folio-org.atlassian.net/browse/ERM-788

Owen Stephens

  • Owen to review how JSON Patch standard may be used to address this

https://folio-org.atlassian.net/browse/UXPROD-2124

https://folio-org.atlassian.net/browse/ERM-793 / https://folio-org.atlassian.net/browse/ERM-794 / https://folio-org.atlassian.net/browse/ERM-795

Ethan Freestone (Deactivated)

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

 

 

https://folio-org.atlassian.net/browse/UXPROD-2344

https://folio-org.atlassian.net/browse/ERM-800

steve.osguthorpe

 

https://folio-org.atlassian.net/browse/UXPROD-2344

https://folio-org.atlassian.net/browse/ERM-807

Owen Stephens / Peter Böhm

Add embargo info to JSON and KBART export formats. 

  • JSON: separate representions

  • KBART: single string

Will be ready to progress for when Peter returns on Wednesday.