Sprint Goal / Focus

Sprint Schedule

Sprint: 180
- Start Mon 20 Nov 2023
- Finish Fri 1 Dec
- Sprint Board
- Jira Sprint: 1993
- Sprint Report
Release: 2023.2 Poppy
- Sprint ???: Bugfix Release Deadline (---) [FOLREL-581]
Release: 2024.1 Quesnalia
- Sprint 5 of 11 since Release Development Cycle Starts (Sprint 176) to Feature Freeze (Sprint 186: 15 Mar 2024)
- Sprint 187: Module Release Deadline (22 Mar 2024) [FOLREL-565]
- Sprint 189: Bugfix Release Deadline (19 Apr 2024) [FOLREL-581]

Development Meetings

Mon 11 Dec
Wed 13 Dec

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

Lead Roles:

Code Review: @Ethan Freestone
QA: @Owen Stephens

QA Environment:

folio-snapshot, folio-snapshot-2

Present

@Jag Goraya
@Ethan Freestone
@Monireh Rasouli
@Jack Golding
@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 Tests
  - 3.1.2 Release Tasks (Non-Flower Release)
  - 3.1.3 Release Tasks (Orchid CSP)
  - 3.1.4 Release Tasks (Poppy Bug Fix)
  - 3.1.5 Maintenance
- 3.2 Changes
- 3.3 Rolled Over From Previous Sprint
  - 3.3.1 In Development
  - 3.3.2 Sprint Backlog
  - 3.3.3 Blocked
  - 3.3.4 In QA
  - 3.3.5 For Elaboration
  - 3.3.6 For Release Prep / Pending Testrails
  - 3.3.7 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

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
SI-34: Dashboard fails if any module fails to respond to /servint/widgets/definitions/global Closed		Pending release decision on SI-38 for grails-okapi Revisit in Sprint 180 Release Target: Quesnalia
ERM-3089: missing content-type header in /licenses/licenses/${uuid}/linkedAgreements responseClosed		Pending release decision on SI-38 for grails-okapi Revisit in Sprint 180 Release Target: Quesnalia
ERM-3078: SPIKE: Investigate version conflict handling in agreements/licensesClosed	@Jack Golding	Triage Aim of ERM-1981 was to prevent overwriting updates Major version of Grails since then, which has somehow broken the conflict resolution Approach Use postman to check prevent version conflict handling Check ERM-1981 for handling code placement Check current Grails documentation 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/ERM-3119	@Claudia Malzer	Current State Cannot retrieve status In Code Review TODO Check handle link org Use greyed out organisation Development Estimate: NA
https://folio-org.atlassian.net/browse/ERM-3120		Triage Approach Will require additional has/has not filter 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/ERM-3121		Triage simple search schema defines number_of_rows, with default but no max value Approach add frontend bounds of 1 and 100 Components and Changes Frontend: ui-dashboard Backend: NA Tests / Data / Dependencies: add new test Known Unknowns: NA QA: snapshot Release Target: Quesnalia Development Estimate
https://folio-org.atlassian.net/browse/ERM-3122		Triage Focus jumps to last autofocus by default Approach Add custom focus handling Check how focus is handled in agreements and licenses Components and Changes Frontend Backend Tests / Data / Dependencies Known Unknowns QA: snapshot \| local \| testing \| other Release Target: Development Estimate

Tests

Cypress test development stalled pending implementation of https://folio-org.atlassian.net/browse/STCOR-484

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-2813

Release Tasks (Non-Flower Release)

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-3094		Not required now, as Poppy backport has been introduced

Release Tasks (Orchid CSP)

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA

Release Tasks (Poppy Bug Fix)

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
NA

Changes

Added

Removed: note whether rescheduled or deferred

Feature ID	Issue ID	Change	Notes

Feature ID	Issue ID	Change	Notes

Rolled Over From Previous Sprint