Sprint Goal / Focus

Bug Fix
Package

Sprint Schedule

Sprint: 157
- Start Mon 16 Jan 2023
- Finish Fri 27 Jan
- Sprint Board
- Jira Sprint: 1516
- Sprint Report
Release: 2023.1 Orchid
- Sprint 7 of 8 since Release Development Cycle Starts (Sprint 151) to Feature Freeze (Sprint 158)
- Sprint 159: Module Release Deadline [FOLREL-???]
  - Backend 22 Feb 2023
  - Frontend 24 Feb 2023
- Sprint: Bugfix Release Deadline (31 Mar 2023) [FOLREL-???]

Development Meetings

18 Jan
23 Jan 2023 (Mid Sprint Review)
25 Jan

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

Owen: off Wed
Jag: OOO Tue-Fri

Lead Roles:

Code Review: @Ethan Freestone
QA: @Owen Stephens

QA Environment:

folio-snapshot

Present

@Jag Goraya
@Ethan Freestone
@Owen Stephens
@Claudia Malzer
@Monireh Rasouli

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 No Feature
  - 3.1.2
  - 3.1.3 Release Tasks (Orchid)
  - 3.1.4 Release Tasks (Morning Glory Hotfix)
  - 3.1.5 Release Tasks (Nolana Hotfix)
  - 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 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
  - 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

No Feature

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-2514	@Owen Stephens	Further triage required. May be a client rather than API issue, where the client is not updating as expected. Triage Confirmed when three-part referenceId used Approach SubscriptionAgreementController.groovy line 53ff: switch disjunctiveReference from final Components and Changes Frontend: NA Backend: mod-agreements Tests / Data / Dependencies: potentially add new integration lookup test Known Unknowns: NA QA: snapshot Release Target: Orchid Development Estimate:
https://folio-org.atlassian.net/browse/ERM-2474	@Owen Stephens
https://folio-org.atlassian.net/browse/ERM-2547	@Ethan Freestone	Approach Backport changes made for Orchid to Nolana need to pick right versions of stripes-kint-componets Components and Changes Frontend: stripes-erm-components, ui-agreements, ui-licenses QA: snapshot Development Estimate: 0.25d+ release
https://folio-org.atlassian.net/browse/ERM-2538	@Ethan Freestone	Approach Backport changes made for Orchid to Nolana need to pick right versions of stripes-kint-componets Components and Changes Frontend: stripes-erm-components, ui-agreements, ui-licenses QA: snapshot Development Estimate: 0.25d+ release
https://folio-org.atlassian.net/browse/ERM-2550		Triage resulting from a breaking change in upgrading to SKC 4 this makes backporting to Nolana (SKC 3) very difficult this makes backporting to Morning Glory (SKC 2) almost impossible Approach for MG/N: add encoding patch rather than backport the current fix use encodeURI component directly on the match term, checking it works with &, ", % and ? check how double encoding works when then encoded if this doesn't work, will need to manually swap out problem text Components and Changes Frontend: all frontend components Backend: NA Tests / Data Dependencies Known Unknowns QA: other Development Estimate: 7d+
https://folio-org.atlassian.net/browse/ERM-2554	@Ethan Freestone	Triage default keyboard shortcuts are imported in agreements, but use app-specific shortcuts (as per lkb) console.log app-specific-shortcuts if not, then probably stripes issue Approach remove standalone comparisons file (not in folder) populate history correctly Components and Changes Frontend: ui-erm-comparisons Backend: na Tests / Data Dependencies / Known Unknowns: NA QA: snapshot \| local \| testing \| other Development Estimate
https://folio-org.atlassian.net/browse/ERM-2555	@Monireh Rasouli	Approach adjust comparisonPointFilter logic clear name from that on refresh need same pattern as for agreement line filters Components and Changes Frontend: comparisonPointFilter Backend: NA Tests / Data: NA QA: snapshot Development Estimate: 0.5d
https://folio-org.atlassian.net/browse/ERM-2569	@Ethan Freestone	Triage looks like is is happening on current snapshot will need to backport to previous releases Approach does the created link have the right data? NO are we returning the correct data? is the frontend reading the data correctly? Compare returned agreement in Lotus vs Snapshot if same: frontend issue if different: backend issue Components and Changes Frontend: NA Backend: Tests / Data / Dependencies / Known Unknowns: NA QA: snapshot Release Target: Orchid, Nolana, Morning Glory Development Estimate

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

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-2610	@Claudia Malzer	Approach Components and Changes Frontend: NA Backend Tests / Data expand ingest test Known Unknowns: NA QA: local Development Estimate: 5d
https://folio-org.atlassian.net/browse/ERM-2611		Approach Components and Changes Frontend: NA Backend Tests / Data QA: local, running with harvests should be sufficient Development Estimate: 1d

Release Tasks (Orchid)

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
NA

Release Tasks (Morning Glory Hotfix)

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Release Tasks (Nolana Hotfix)

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

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

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-2488		Triage useEffect doing job of mount handler Approach can input approach be set up differently? is only one id needed, in which case how would stripes handle this across tabs? persistent results wiped across app-tab switching Components and Changes Frontend Backend Tests / Data Dependencies Known Unknowns unknown impacts QA: snapshot \| local \| testing \| other Development Estimate
	@Ethan Freestone	Add test to stripes-kint-components to check encoding of special characters

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