Sprint Goal / Focus

..

Sprint Schedule

Sprint: 166
- Start Mon 22 May 2023
- Finish Fri 2 June
- Sprint Board
- Jira Sprint: 1680
- Sprint Report
Release: 2023.2 Poppy
- Sprint 8 of 9 since Release Development Cycle Starts (Sprint 159) to Feature Freeze (Sprint 167)
- Sprint 168: Module Release Deadline (30 Jun 2023) [FOLREL-565]
- Sprint 171: Bugfix Release Deadline (4 Aug 2023) [FOLREL-581]

Development Meetings

Wed 24 May
Mon 29 May - cancelled
Wed 31 May

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

Mon 29 May: Public Holiday

Lead Roles:

Code Review: Ethan Freestone
QA: Owen Stephens

QA Environment:

folio-snapshot, folio-snapshot-2

Present

Info

title	Planning Questions

Does the issue meet the criteria for Definition of Ready?
What front and back end components are affected?
What changes need to be made? (additions, removals or modifications)
What development tests need to be written?
What data does the developer need to verify their work?
What are the known unknowns?
What is needed to QA? (environment, data, scripts)

Navigation

Table of Contents

Expand

title	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

- not ready

- pending triage / planning

Sprint Focus

Info

icon	false
title	Planning Notes Template

Triage
Approach
Components and Changes
- Frontend
- Backend
Tests / Data / Dependencies
Known Unknowns
QA: snapshot | local | testing | other
Release Target:
Development Estimate

jira

FEATURE

serverSystem JiraserverId01505d01-b853-3c2e-90f1-ee9b165564fckeyUXPROD-3890

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

No Feature

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-24212923

Jack Golding

Triage

performance issues from inline edit, which can stop agreement loading

Approach
- Scenario 4:
  - same behind-the-scenes behaviour (with minimal details to create agreement), but without taking user out of context
  - won't be using existing agreement form
- use query-parameter to not expand agreement lines in edit view (introduced in ERM-2888)
- remove call that renders cards
- implement basket changes
- leave in place the mechanism that allows us to add agreement linesreview for deprecation once replacement functionality is describedshould be able to add fields to
  - domain classes
  - migrations
- check what happens to dataCreated
- add metadata component to frontend
- reuse PCI view
Components and Changes
- Frontend: use stripes-erm-components metadata component in ui-agreements TitleView
- Backend: nonemod-agreements
Tests / Data / Dependencies
- related: ERM-2892
- update cypress test set up for ERM-2773
Known Unknowns: NA
QA: snapshot
Known Unknowns
- check what happens to dateCreated (could be first dateUpdated)
- what happens with / how does GORM handle an change in collection?
- does package get updated if title is updated?
QA: snapshot | local | testing | other
- risk of false positive / negative: check behaviour when no change has been made
Release Target: Poppy
Development Estimate: 1d

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2919

Ethan Freestone

Issue ID

Sprint Backlog?

Approach
- Truncate note to prevent ingest failure
- Re-use or apply truncation pattern
Components and Changes
- Backend: mod-agreements
QA: snapshot | local | testing | other
Release Target: Poppy
Development Estimate: 2d

No Feature

<0.5d

Tests

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA

Release Tasks (Poppy)

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA

Release Tasks (Non-Flower Release)

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA

Maintenance

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA

Changes

Added

Removed: note whether rescheduled or deferred

Feature ID	Issue ID	Change	Notes

Rolled Over From Previous Sprint

Info

title	Planning Notes Template

Current State
TODO
Development Estimate

In Development

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2641

Ethan Freestone

Current State
- license, SI and plugins seem to function
- new issues arising with mod-agreements (liquibase, hibernate)
  concern that they may have been missed previouslymaven is back up, so unblicked
TODO
- inspect hibernate and liquibase versions for discrepancies
Development Estimate
- handover to Steve this week

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2926

Ethan Freestone

For Code Review

Claudia Malzer

Current State
TODO
Development Estimate

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UXPROD-3890

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2421

Jack Golding

Current State
- Scenarios 1-3 done
TODO
- Development Estimate
- Triage
  - performance issues from inline edit, which can stop agreement loading
- Approach
  - Scenario 4:
    - same behind-the-scenes behaviour (with minimal details to create agreement), but without taking user out of context
    - won't be using existing agreement form
  - use query-parameter to not expand agreement lines in edit view (introduced in ERM-2888)
  - remove call that renders cards
  - implement basket changes
  - leave in place the mechanism that allows us to add agreement lines
    - review for deprecation once replacement functionality is described
- Components and Changes
  - Frontend: ui-agreements
  - Backend: none
- Tests / Data / Dependencies
  - related: ERM-2892
  - update cypress test set up for ERM-2773
- Known Unknowns: NA
- QA: snapshot
- Release Target: Poppy
- Development Estimate: 2d
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2903

Ethan Freestone

For Code Review

- finish modal on scenario 4
Development Estimate
- end of day

Sprint Backlog

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2630

/

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2905

Ethan Freestone

Current State
- ERM-2916 mostly done
TODO
- ERM-2916 final
- ERM-2917 not started
Development Estimate: expected today

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-4233

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2918

Ethan Freestone

For joint QA with Owen

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2920

Current State
TODO: use useBatchedFetch hook
Development Estimate: Wed

Blocked

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

In QA

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2790

Owen Stephens

Questions arising from QA/review

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2903

Owen Stephens

For Elaboration

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

For Release Prep / Pending Testrails

Cross-check against e2e Jira issues

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

Bugfix Cycle

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

Sprint Summary

ERM

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,assignee,status,components
columns	key,summary,type,assignee,status,components
maximumIssues	20
jqlQuery	labels != release and labels in (licenses, agreements, erm) and Sprint = 1679 and issuetype in standardIssueTypes()
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Dashboard

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,assignee,status,components
columns	key,summary,type,assignee,status,components
maximumIssues	20
jqlQuery	labels = dashboard and Sprint = 1679
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Other

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,assignee,status,components,labels
columns	key,summary,type,assignee,status,components,labels
maximumIssues	20
jqlQuery	(labels = release or labels not in (licenses, agreements, erm, dashboard)) and Sprint = 1679
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

No Label

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,assignee,status,components
columns	key,summary,type,assignee,status,components
maximumIssues	20
jqlQuery	labels is empty and Sprint = 1679
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Versions Compared

Old Version 1

New Version 2

Key

Sprint Goal / Focus

Sprint Schedule

Sprint Capacity

Sprint Focus

FEATURE

No Feature

No Feature

Tests

Release Tasks (Poppy)

Release Tasks (Non-Flower Release)

Maintenance

Changes

Rolled Over From Previous Sprint

In Development

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UXPROD-3890

Sprint Backlog

Blocked

In QA

For Elaboration

For Release Prep / Pending Testrails

Bugfix Cycle

Sprint Summary

ERM

Dashboard

Other

No Label

Page Comparison

Versions Compared

Old Version 1

New Version 2

Key

Sprint Goal / Focus

Sprint Schedule

Sprint Capacity

Sprint Focus

FEATURE

No Feature

No Feature

Tests

Release Tasks (Poppy)

Release Tasks (Non-Flower Release)

Maintenance

Changes

Rolled Over From Previous Sprint

In Development

Jira LegacyserverSystem JiraserverId01505d01-b853-3c2e-90f1-ee9b165564fckeyUXPROD-3890

Sprint Backlog

Blocked

In QA

For Elaboration

For Release Prep / Pending Testrails

Bugfix Cycle

Sprint Summary

ERM

Dashboard

Other

No Label

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UXPROD-3890