Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 AvailabilitySchedule | 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:

QA Environment: folio-testing

Navigation

Table of Contents

Expand
titleSprint Planning Agenda
  1. Sprint Goal / Focus
  2. Sprint Capacity
  3. Review sprint candidates 
  4. Agree technical approach / define key implementation tasks
  5. Finalise estimates / costings
  6. Confirm sprint scope
  7. Confirm first actions



Sprint Planning  

(error) - not in sprint

(tick) or @ - in sprint 

 

Backend unblockers (steve.osguthorpe ):

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-800
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-779
    Jira Legacy
    serverSystem Jira
    JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-748
     / 
    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-777
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-827
     / 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-828
    814

Sprint Candidates

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2347

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-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.

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2267

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-827
 / 
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-828

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.

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2352

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-829
 

(error)(error)

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. 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2352

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-779

Backend - 5 minutes.

Trivial backend model to replicate


Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-694


Brought Forward

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2124

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-547

PR raised - ready for code review?

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2346

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-748

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

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2345

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-777

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

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2344

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-805


Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2124

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-788

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

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2124

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-793
 / 
Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-794
 / 
Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-795

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



Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2344

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-800


Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2344

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-807

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.