Sprint Goal / Focus

Sprint Schedule

Sprint: 72
Release: Elderflower
Quarter: 2019 Q3
Start Monday 9 Sep, 2pm UK
Finish Friday 20 Sep, 12pm UK

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

Module Release Prep / Deadline: 11 Sep

Lead Roles:

Front End Code Review: @md331 (Deactivated)
Back End Code Review: @steve.osguthorpe
QA: @Owen Stephens

QA Environment: folio-testing

Navigation

1 Sprint Goal / Focus
2 Sprint Schedule
3 Sprint Capacity
4 Sprint Planning
- 4.1 Sprint Focus
- 4.2 Brought Forward

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

Sprint Focus

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-1472	https://folio-org.atlassian.net/browse/ERM-428	@steve.osguthorpe @md331 (Deactivated)	"Current" status is being used to test logic, which may cause internationalisation problems, if using label/value. To avoid this, would need a feature to configure {agreement/link} status Ideally, we distinguish between configurable vs editable refdata @Jag Goraya Create new issue to define, for each refdata set, whether configurable/editable, and implications TODO: BE: Store amendment link status and notes (1d) mirror how license links are handled nested rather than at same level to support easier front-end handling amendment link array, with amendments sorted in start date descending order FE: implement form and error (3d)
https://folio-org.atlassian.net/browse/UXPROD-1472	https://folio-org.atlassian.net/browse/ERM-429	@md331 (Deactivated)	FE: 3d including integration tests Amendment notes are presented in UI mockup differently to how notes are handled for future/past licenses. @Gill Osguthorpeto confirm that whether we should keep/break consistency. From @Gill Osguthorpe : I'm not sure what I'm comparing, could someone confirm please @Jag Goraya, @md331 (Deactivated)
https://folio-org.atlassian.net/browse/UXPROD-1472	https://folio-org.atlassian.net/browse/ERM-430	@steve.osguthorpe	BE: 1d to configure rules Added https://folio-org.atlassian.net/browse/ERM-441
https://folio-org.atlassian.net/browse/UXPROD-585	https://folio-org.atlassian.net/browse/ERM-395	@Peter Böhm	BE: 2d @steve.osguthorpe to add signposting to classes
https://folio-org.atlassian.net/browse/UXPROD-585	https://folio-org.atlassian.net/browse/ERM-394	@steve.osguthorpe	BE: 0.5d FE: 0.25d TODO: Extend existing filters to include date range Missing dates are treated as included, so would need to include NULL check FE: update calls to revised endpoints
https://folio-org.atlassian.net/browse/UXPROD-585	https://folio-org.atlassian.net/browse/ERM-392	@John Fereira	Existing pattern of counts logging - number of upserts Non-trivial maybe is handling single title services
https://folio-org.atlassian.net/browse/UXPROD-585	https://folio-org.atlassian.net/browse/ERM-393	@steve.osguthorpe
	https://folio-org.atlassian.net/browse/ERM-371		@Owen Stephens to revisit with @Gill Osguthorpe
	https://folio-org.atlassian.net/browse/ERM-422	@Claudia Malzer	Is this person AND role, or is it person OR role?

Brought Forward

Feature ID	Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-356 / https://folio-org.atlassian.net/browse/ERM-361	@John Fereira	Estimate: 2d Aim to prioritise to meet module release deadline to include in Daisy release.
https://folio-org.atlassian.net/browse/ERM-217	@Owen Stephens
https://folio-org.atlassian.net/browse/ERM-338	@Owen Stephens
https://folio-org.atlassian.net/browse/ERM-182	@Owen Stephens
https://folio-org.atlassian.net/browse/ERM-440	@Owen Stephens
https://folio-org.atlassian.net/browse/ERM-438	@Felix Hemme

ERM Sprint 72