Sprint Goal / Focus

NA

Sprint Schedule

Sprint: 170
- Start Wed 30 Aug 2023
- Finish Fri 8 Sep
- Sprint Board
- Jira Sprint: 1807
- Sprint Report
Release: 2023.2 Poppy
- Sprint 15 of 17 since Release Development Cycle Starts (Sprint 159) to Feature Freeze (Sprint 175: 6 Oct 2023)
- Sprint 176: Module Release Deadline (13 Oct 2023) [FOLREL-565]
- Sprint 178: Bugfix Release Deadline (10 Nov 2023) [FOLREL-581]

Development Meetings

Wed 30 Aug
Mon 4 Sep
Wed 8 Sep

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

Monireh: back Mon 4 Sep

Lead Roles:

Code Review: @Ethan Freestone
QA: @Owen Stephens

QA Environment:

folio-snapshot, folio-snapshot-2

Present

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

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 No Feature
  - 3.1.3 Tests
  - 3.1.4 Release Tasks (Flower Release / CSP)
  - 3.1.5 Release Tasks (Non-Flower Release)
  - 3.1.6 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

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

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-3010	@Jack Golding	Triage Approach Use `has` and `has not` instead of 1 or 0, etc use default logic of AND taking precedence over OR preserve filter state in url AND/OR filter options cannot be added until validated no ux for non-valid filters in ERM Use apply button to trigger validation only if needed. Clear invalid filters May need arrayMutators in a form for field arrays Components and Changes Frontend: ui-agreements, may need changes to SKC Backend: NA Tests / Data / Dependencies add unit test on new filter component interactors for future integration tests Known Unknowns: final-form or form: if ff, will need state arrays QA: snapshot Release Target: Poppy Development Estimate

No Feature

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-3014	@Claudia Malzer	Approach parallel batch fetch users (and user names), using component from stripes-erm-component pagination is complicated for users as user fetching is an upfront check for permission verification - fetch 100 at a time, without max limit (ie, use default of infinity) Components and Changes Frontend: ui-dashboard Backend: none Tests / Data / Dependencies: NA Known Unknowns: NA QA: snapshot Release Target: Poppy Development Estimate:
https://folio-org.atlassian.net/browse/ERM-3018		This would enable pushKb testing against Gokb data sources, independent of FOLIO release cycles Triage migration - what to do with existing titles ingest from multiple sources: preventing title duplication currently don't save gokb uuid would be three cycles before using id class 1 namespaces are not checked in any breaking/switching order, so title would have to be promoted as first match check (though that would remove then re-add titles) More discussion needed to thrash out consequences.
https://folio-org.atlassian.net/browse/ERM-3012		May not be technically feasible. Needs investigation to determine approach. `relationshipTypes` will need to become frontend translations Cannot currently be omitted/suppressed from picklist dropdowns (as this is dynamically generated) Not expecting these to be user editable In the future (so out of scope now), instead of using as refdata, should use domain class that uses refdata for the relationship types.
https://folio-org.atlassian.net/browse/ERM-3013	@Claudia Malzer
https://folio-org.atlassian.net/browse/ERM-3017		DRAFT
https://folio-org.atlassian.net/browse/SI-34		DRAFT

Tests

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA

Release Tasks (Flower Release / 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

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

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-2841	@Ethan Freestone	For Code Review
https://folio-org.atlassian.net/browse/UXPROD-3890	https://folio-org.atlassian.net/browse/ERM-2992	@Ethan Freestone	For Code Review
	https://folio-org.atlassian.net/browse/ERM-3016	@Ethan Freestone	Will merge with ERM-2937

Sprint Backlog

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

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

Blocked

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

Blocked by https://folio-org.atlassian.net/browse/STSMACOM-775

Will need some limited regression testing if stripes components changes are merged

In QA

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-2989 https://folio-org.atlassian.net/browse/ERM-2994 https://folio-org.atlassian.net/browse/ERM-2995 https://folio-org.atlassian.net/browse/ERM-2988 https://folio-org.atlassian.net/browse/ERM-2990 https://folio-org.atlassian.net/browse/ERM-2987 https://folio-org.atlassian.net/browse/ERM-2991 https://folio-org.atlassian.net/browse/ERM-2984 https://folio-org.atlassian.net/browse/ERM-2985 https://folio-org.atlassian.net/browse/ERM-2986 https://folio-org.atlassian.net/browse/ERM-2996 https://folio-org.atlassian.net/browse/ERM-2997 https://folio-org.atlassian.net/browse/ERM-2998
	https://folio-org.atlassian.net/browse/ERM-2641
	https://folio-org.atlassian.net/browse/ERM-2934
	https://folio-org.atlassian.net/browse/ERM-2922
	https://folio-org.atlassian.net/browse/ERM-1795
	https://folio-org.atlassian.net/browse/ERM-2189
	https://folio-org.atlassian.net/browse/ERM-2630		Initial testing worked so far - successfully pushed package info. TODO: Add test plan info to issue (started)
	https://folio-org.atlassian.net/browse/ERM-2815
	https://folio-org.atlassian.net/browse/ERM-2966
	https://folio-org.atlassian.net/browse/ERM-2967
	https://folio-org.atlassian.net/browse/ERM-2973
	https://folio-org.atlassian.net/browse/ERM-2979
	https://folio-org.atlassian.net/browse/ERM-2980
	https://folio-org.atlassian.net/browse/ERM-2993

For Elaboration

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

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

For Release Prep / Pending Testrails

Cross-check against e2e Jira issues

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-2421
	https://folio-org.atlassian.net/browse/ERM-1110
	https://folio-org.atlassian.net/browse/ERM-2628

ERM Sprint 173