Sprint Goal / Focus

Dashboard Base Setup
RTL Migration
Agreement Date
Subscription Controller

Sprint Schedule

Sprint: 106
Release: Iris
Quarter: 2021 Q1
Start Monday 18 Jan
Finish Friday 29 Jan

Note: Iris release has been delayed to May.

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

18 Jan: Adi off (MLK Day)

Lead Roles:

Front End Code Review: Aditya matukumalli
Back End Code Review: Ethan Freestone
QA: Owen Stephens

QA Environment: folio-snapshot

Navigation

Sprint Planning Agenda

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
UXPROD-612 - Getting issue details... STATUS	ERM-1529 - Getting issue details... STATUS	Ethan Freestone Ian Ibbotson (Use this one)
UXPROD-612 - Getting issue details... STATUS	ERM-1528 - Getting issue details... STATUS	Ethan Freestone
	ERM-1530 - Getting issue details... STATUS	Blocked
UXPROD-2870 - Getting issue details... STATUS	ERM-1531 - Getting issue details... STATUS		Frontend: 0.5d. Backend: None. Aim to simplify period display. Reuses existing data points. Replaces existing UI, rather than show both. TODO: Remove existing current period conditional. Reposition in template.
UXPROD-2870 - Getting issue details... STATUS	ERM-1533 - Getting issue details... STATUS / ERM-1532 - Getting issue details... STATUS		Backend: 2d. Frontend: 1d May need change in the way dates are stored. Potentially need to be non-transient, as they will need to be searchable. TODO: Save start and end dates to database on record save Set up nightly timer task to update existing data check update existing timer task to not use existing housekeeping endpoint check Update MCL to pull in correct date Add search date components to SaS screen Mid Sprint Update: 1533: frontend was just a label change, as backend already using start/end dates other backend work has passed code review and is merged 1532: may require some re-iteration to make robust and compatible with a shared component, including better naming and checkbox usage for logic handling
UXPROD-2870 - Getting issue details... STATUS	ERM-1534 - Getting issue details... STATUS		Backend: . Frontend: . Preferred route would be a breaking API change. Add mechanism to catch and convey Next Period. Use some kind of period marker for current, next and previous. Add filter based on marker. Further discussion required. Could just show current period as a minimal change. Could automatically expand All Periods accordian.

Brought Forward

Feature ID	Issue ID	Sprint Backlog?	Notes / Estimates / Actions
FAT-81 - Getting issue details... STATUS	ERM-1265 - Getting issue details... STATUS	Ethan Freestone	On hold. Pending decision re interactors.
FAT-81 - Getting issue details... STATUS	ERM-1277 - Getting issue details... STATUS	Aditya matukumalli
FAT-81 - Getting issue details... STATUS	ERM-1526 - Getting issue details... STATUS	Aditya matukumalli
UXPROD-2812 - Getting issue details... STATUS	ERM-1239 - Getting issue details... STATUS	Claudia Malzer	Error `Cannot read property 'contains' of null` applying the changes to ui-licenses. If issue is not at ui-licenses app list, then need to interrogate CommandList from stripes component, Breakpoint at failing line for hotkeys.js
UXPROD-2811 - Getting issue details... STATUS	ERM-1240 - Getting issue details... STATUS	Claudia Malzer
UXPROD-2857 - Getting issue details... STATUS	ERM-1241 - Getting issue details... STATUS	Claudia Malzer
FAT-81 - Getting issue details... STATUS	ERM-1274 - Getting issue details... STATUS	Aditya matukumalli	Some rework on how ERM consumes the components.
UXPROD-2817 - Getting issue details... STATUS	ERM-1459 - Getting issue details... STATUS	Ian Ibbotson (Use this one)	TODO: Review Owen's feedback Review current implementation against defined requirements Review test data for use Confirm work breakdown for implementation in Jira ticket Test data provided would work for manual approach ... should really be automated and done as part of integration test suite.