Versions Compared

Key

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

Sprint Goal / Focus

  •  

Sprint Schedule

  • Sprint: 95
  • Release: Honeysuckle
  • Quarter: 2020 Q3
  • Start Monday 27 July, 2pm UK
  • Finish Friday 14 Aug, 12pm UK


Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Ian / Owen away 3-14 Aug
  • Steve away all sprint

Lead Roles:

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

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 

 

Brought Forward

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

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

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

(error)

For Release -> Done, with spinoffs.

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keySTCOM-722
     for MCL Title / Popover issue (Stripes)
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1026
    raised for Capitalise on Overlap column - low priority
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1025
     raised for quotation mark in Tooltip and MCL

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

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

(error)For Release -> Done

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

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

Merged for QA. 

  • `Name + ID` saved in the `Name` field - may need to be separated in future.
  • Using long name for display in the meantime.

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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-943
 /  
Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-944
 / 
Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-945

Done: 

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

TODO:

  • Migrations are tricky. Using some examples from previous migration scripts. Can use Groovy rather than SQL if preferable, though SQL 
  • Save and then change 

Specification is sufficient for now.

  • Claudia to review ERM-944 and ERM-945 this week in case additional clarifications are needed

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

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

Works alongside 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-1003
to deliver 
Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-2440

  • Uses same pattern as adding an amendment at accordian level. 
  • Where resource is not specified, see wireframe. 
  • Basket / eHoldings option visible depending on tenant settings for KB sources
  • Cannot delete or re-link resource after it has been created
  • User must choose a resource OR fill out a description 

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

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

Back-end has been done for this. 

Merged into ERM-1000 as a subtask. 

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

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

Aditya matukumalli

Similar code area as ERM-1000, but not part of that functionality. 

Adi to pick up to avoid code conflict. 

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

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

1d

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

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

Ethan Freestone

1d

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

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

(error)

Sprint Focus

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

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

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

To pick this off before ERM-1000

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

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

In QA

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

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

In Progress

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

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

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. 


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

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

Steve

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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-1006
Ethan / Steve

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

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

Peter / Steve 

To follow ERM-1010. 

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

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

Steve


Brought In

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


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

Comparison reports are not loading quickly enough, eg partials. 
  • Consider alternatives to storing large reports, eg,
    • potentially chunk up and then paginate the JSON output, similar to eresources?
    • stream report outputs?
  • What would be the impact to reengineering existing functionality to handle this differently?
  • Are there other modules that need to deal with similarly large JSON outputs?

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

Duplicate coverage array


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


Code is async based on promises. So fetch doesn't support linear process. Could make this use of endpoints tricky.

Relates to 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyCHAL-208
.

Ian to discuss with Steve. If progressable potentially with Ethan. 


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

Ethan FreestoneProgressable. Need to work out mod-config

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

Investigation piece. If it cannot be fixed, remove the sort options from the UI.

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

Done and done.

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

Ready to progress

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

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. 


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



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



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

Claudia Malzer

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

Change agreement search to unlink Organisation and Content Provider filters.

Maybe affected by https://folio-project.slack.com/archives/CAYCU07SN/p1595238491191800


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

Simple change to extend matched fields for Search

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

Claudia MalzerSimple change to extend matched fields for Search

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

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

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

Should be able to progress a solution (if not a perfect or FOLIO wide solution)

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


(error)
Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-1048
 / 
Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-1047

Could do with technical review and assess approach.  Best to leave until II and OS return

UX Improvements


Comparisons Feedback



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

(question)Potentially transfer to Ethan ...