Sprint Goal / Focus

Poppy Feature Freeze

Sprint Schedule

Sprint: 167
- Start Mon 5 June 2023
- Finish Fri 16 June
- Sprint Board
- Jira Sprint: 1681
- Sprint Report
Release: 2023.2 Poppy
- Sprint 9 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 7 Jun
Mon 12 Jun
Wed 14 Jun

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

NA

Lead Roles:

Code Review: @Ethan Freestone
QA: @Owen Stephens

QA Environment:

folio-snapshot, folio-snapshot-2

Present

@Jag Goraya
@Ethan Freestone
@Jack Golding
@Owen Stephens
@Claudia Malzer

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

1 Sprint Goal / Focus
2 Sprint Schedule
3 Sprint Capacity
- 3.1 Sprint Focus
  - 3.1.1
  - 3.1.2 FEATURE
  - 3.1.3 No Feature
  - 3.1.4 Tests
  - 3.1.5 Release Tasks (Nolana CSP)
  - 3.1.6 Release Tasks (Non-Flower Release)
  - 3.1.7 Maintenance
- 3.2 Changes
- 3.3 Rolled Over From Previous Sprint
  - - 3.3.1.1 In Development
    - 3.3.1.2 Sprint Backlog
  - 3.3.2
    - 3.3.2.1 Blocked
    - 3.3.2.2 In QA
    - 3.3.2.3 For Elaboration
    - 3.3.2.4 For Release Prep / Pending Testrails
    - 3.3.2.5 Bugfix Cycle
4 Sprint Summary
- 4.1 ERM
- 4.2 Dashboard
- 4.3 Other
- 4.4 No Label

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

Planning Notes Template

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

https://folio-org.atlassian.net/browse/UXPROD-4333

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-2934	@Jack Golding	Triage Approach Add JSON file Review ERM-1651 for example from Agreements Review mod-service-interaction to see how that consumes the file Components and Changes Frontend Backend Tests / Data / Dependencies Known Unknowns QA: snapshot \| local \| testing \| other Release Target: Development Estimate

FEATURE

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
	https://folio-org.atlassian.net/browse/ERM-2630	Current State ERM-2916 mostly done TODO ERM-2916 final ERM-2917 not started Look at title push Development Estimate: expected today

No Feature

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-2935		Triage React thinks the import is an object not a function Fix is available, but changes the pattern used everywhere doesn't inform the cause, so we don't have any better understanding of what the issue really is Approach further diagnosis by individually pinning dependencies start with non-folio deps Components and Changes Frontend Backend Tests / Data / Dependencies Known Unknowns: all of it QA: snapshot Release Target: Poppy Development Estimate: ?

Tests

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA

Release Tasks (Nolana CSP)

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA

Release Tasks (Non-Flower Release)

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA

Maintenance

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-2911		Current State Number Generator feature pending TODO Release SKC after NumGen changes made Development Estimate: Minimal- This sprint

Changes

Added

Removed: note whether rescheduled or deferred

Feature ID	Issue ID	Change	Notes

Feature ID	Issue ID	Change	Notes
https://folio-org.atlassian.net/browse/UXPROD-4340	https://folio-org.atlassian.net/browse/ERM-2937	@Claudia Malzer	Approach change on route multiple to single fetch get value of offset to drive which page to get check impacts of updates for next/prev focus shift new pattern that can be applied to other related issues no change to limit setting (ie, via constant) Components and Changes Frontend: ui-agreements Backend: none Tests / Data / Dependencies: NA Known Unknowns: NA QA: snapshot Release Target: Poppy Development Estimate:
	https://folio-org.atlassian.net/browse/SI-23	@Ethan Freestone

Rolled Over From Previous Sprint

Planning Notes Template

Current State
TODO
Development Estimate

In Development

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

Feature ID	Issue ID	Sprint Backlog?	Notes / Estimates / Actions
	https://folio-org.atlassian.net/browse/ERM-2641	@Ethan Freestone	Current State migrations are not accessible in a production docker build TODO Steve to look into why the jar isn't building Development Estimate ??
https://folio-org.atlassian.net/browse/UXPROD-4271	https://folio-org.atlassian.net/browse/ERM-2923	@Claudia Malzer	Current State frontend part is done input from Steve re bubbling up changes in hierarchy Removed from scope: changes to identifier or coverage TODO handle database change by listening for identifier change at tip of domain classes (eg, TI, PTI etc), and bubble up changes to parent in hierarchy Add event listener for when a TI identifier is updated or created, the parent object should grab that last updated of the identifier and trigger a save of the parent object Development Estimate ?

Sprint Backlog

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-3890

https://folio-org.atlassian.net/browse/ERM-2421

@Jack Golding

Current State
- Dev complete. PR reviewed. Design change requested.
TODO
- Move agreement POST to the modal instead of basket route, as the basket shouldn't logically handle that for an agreement.
- Move agreement PUT to form level
Development Estimate
- end of day

Blocked

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

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

In QA

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

Feature ID	Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA	https://folio-org.atlassian.net/browse/ERM-2790	@Owen Stephens	Questions arising from QA/review

For Elaboration

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