Versions Compared

Key

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

Sprint Goal / Focus

  •  Bug fixes for Edelweiss

Sprint Schedule

  • Sprint: 78
  • Release: Edelweiss
  • Quarter: 2019 Q4
  • Start Monday 2 Dec, 2pm UK
  • Finish Friday 13 Dec, 12pm UK


Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

Lead Roles:

  • Front End Code Review: 
  • Back End Code Review:  
  • QA: 

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 

 

Priorities for Edelweiss

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1943

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-621

Missing functionality in 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-376
.

Cannot use /export/ endpoint on its own, as current resources are missing. 

TODO:

  • confirm that license terms (esp controlling license) is presented
  • is the recent extension to the GSON template causing an issue or conflict?
  • Is something like the _SubscriptionAgreement.gson expand linked license section needed in the export (see conditions in lines 38 and 52)?

 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-623

Blocking QA on export agreement, such as 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-418
.

TODO:

  • Identify last known point it was working (EOD 21 Nov: snapshot)
  • Identify breaking changes to mod-agreements since then
  • Starting point may be around PR 210, 211 (relevant to the export), 212

Expecting that front-end is working as expected. 


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-614

Ian Ibbotson(tick)

Relates to 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-561

Cursor tracks where in the harvest the process got to, so it can pick up from where it should be. 

  • What would the performance impact be on a production environment? Should be fixed as a moderate priority. 
  • Can this be done without executing an HQL query

TODO:

  • Set a from  offset (date/time) at the end of the harvest, to indicate where harvesting has reached
  • Set resumption point of cursor based on the from offset, when restarting
    • could last_check be used instead of cursor resumption? that could be problematic if the runsync erred. 

There's nested transaction mysteries.

Ian Ibbotson to review code and comment on issue.


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-558

TODO:

  • Add disabled attribute 
  • Fix console issue:
    • error on disabled resource filter
    • error thrown on first attempt

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-567

Peter Böhm

Comment left on Jira issue for Steve Osguthorpe

Additional

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-356
 / 
Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-361

(question)Not clear how to test. Need API url. 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-591



Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-568




Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-587



Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-607




Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-625