Sprint Goal / Focus

Feature Freeze

Sprint Schedule

Sprint: 150
- Start Mon 3 Oct
- Finish Fri 14 Oct
- Sprint Board
- Jira Sprint: 1365
- Sprint Report
Release: 2022.3 Nolana
- Sprint 9 of 9 since Release Development Cycle Starts (Sprint 142) to Feature Freeze (Sprint 150)
- Sprint 151: Module Release Deadline [FOLREL-549]
  - Backend 26 Oct 2022
  - Frontend 28 Oct2022
- Sprint: Bugfix Release Deadline (2 Dec 2022) [FOLREL-550]

Development Meetings

5 Oct 2022
10 Oct 2022 (Mid Sprint Review)
12 Oct 2022

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

Peter: A/L available 5, 4, 12-13 Oct
Claudia: Absent all sprint
Ethan: AL 6-12 Oct

Lead Roles:

Code Review: @Ethan Freestone
QA: @Owen Stephens

QA Environment: folio-snapshot

Present

@Jag Goraya
@Monireh Rasouli
@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
  - 3.1.3 No Feature
  - 3.1.4 Release Tasks (Nolana)
  - 3.1.5 Maintenance
- 3.2 Changes
  - 3.2.1 Rolled Over From Previous Sprint
    - 3.2.1.1 In Development
    - 3.2.1.2 Sprint Backlog
    - 3.2.1.3 Blocked
    - 3.2.1.4 In QA
    - 3.2.1.5 For Elaboration
    - 3.2.1.6 For Release Prep
    - 3.2.1.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

Planning Notes Template

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

Sprint Focus

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

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-2370	@Ethan Freestone	Approach review how abstractive enrichment calls work unhook/disconnect gokb specific workflow from enrichment (rather than remove) check boolean for requiresSecondaryEnrichmentCall should be able to just make this false change main body of adaptor to add new fields into schema Components and Changes Frontend: none Backend: gokbOAI adaptor inside mod-agreements Tests / Data: no stream tests Dependencies / Known Unknowns: none QA: snapshot add some seed data to test also to note performance boost/hit Development Estimate: 2d

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

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-2356	@Monireh Rasouli	Approach Store local state to see whether checked or not On Save and Close check state and route accordingly Add this option to the footer to use in New and Edit form May have to change shape of submit handler to transport the state to next stage Components and Changes Frontend: ui-agreements Backend: none Tests / Data: appearance of checkbox Dependencies / Known Unknowns: No QA: snapshot Development Estimate: 2d
https://folio-org.atlassian.net/browse/ERM-2368		Approach use existing pattern to convert string to url optionally include PO line links Components and Changes Frontend: ui-agreements, ViewComponent, FIlterComponent Backend: none Tests / Data: No Dependencies / Known Unknowns: No QA: snapshot Development Estimate: <0.5d
https://folio-org.atlassian.net/browse/ERM-2343	@Ethan Freestone	Approach issue/concern that stripes handles null selection Remove manually set default - should just work then Check that when making call, it sets nothing as same as qindex when all set Components and Changes Frontend: ui-agreements Backend: none Tests / Data: No Dependencies: may be affected by Stripes changes to enable ERM-2342 in STSMACOM-700 Known Unknowns expecting to be problematic with complications around filter resets QA: snapshot Development Estimate: <0.25d if no stripes related fallout

No Feature

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions
https://folio-org.atlassian.net/browse/ERM-2362		Triage category and context are different fields context is just never sent in payload when removing Approach always send down a blank string instead of nothing/null Components and Changes Frontend: stripes-kint-components Backend: none Tests / Data: No Dependencies: duplicated by ERM-2364 Known Unknowns: none QA: snapshot \| bugfest Development Estimate: 0.5d
https://folio-org.atlassian.net/browse/ERM-2364		Triage: duplicate of ERM-2362
https://folio-org.atlassian.net/browse/ERM-2359		In QA - should be resolved as a result of fix in web-toolkit and stripes-kint-component
https://folio-org.atlassian.net/browse/ERM-2360		In QA - should be resolved as a result of fix in web-toolkit and stripes-kint-component
https://folio-org.atlassian.net/browse/ERM-2366		Triage doesn't appear to be a regression - confirmed on Lotus Approach We already split out what we're handling as core and supplementary Key on that to choose whether to display blank Add displayCategory prop to SEC/documentCard default to true set to false in coreDocs (ui-licenses) Components and Changes Frontend: stripes-erm-components, ui-licenses Backend: none Tests / Data: extend SEC/documentCard test for non-empty scenario Dependencies / Known Unknowns: none QA: snapshot Development Estimate: 0.5d
https://folio-org.atlassian.net/browse/ERM-2190		Triage toaster is not handled uniquely by ERM OS to take back to reporter Formatted message in toaster is handled by React but not processed by stripes in an accessible way
https://folio-org.atlassian.net/browse/ERM-2371		Triage done in agreements cannot be backported to Morning Glory previously fixed in 2217 Approach: see line changes Components and Changes Frontend: ui-licenses, ui-agreements Backend: none Tests / Data Dependencies / Known Unknowns: none QA: snapshot Development Estimate: <0.5d
https://folio-org.atlassian.net/browse/ERM-2350		Approach Replace empty div with name of component Components and Changes Frontend: ui=dashnb Backend Tests / Data: ? Dependencies / Known Unknowns: none QA: snapshot \| local \| testing \| other Development Estimate: <0.5d

Release Tasks (Nolana)

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Maintenance

Issue ID	Sprint Backlog?	Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

@Ethan Freestone

Defer to end of 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/ERM-2373
	https://folio-org.atlassian.net/browse/ERM-2374
	https://folio-org.atlassian.net/browse/ERM-2375
	https://folio-org.atlassian.net/browse/ERM-2376
	https://folio-org.atlassian.net/browse/ERM-2379
	https://folio-org.atlassian.net/browse/ERM-2380
	https://folio-org.atlassian.net/browse/ERM-2377
	https://folio-org.atlassian.net/browse/ERM-2379
	https://folio-org.atlassian.net/browse/ERM-2380
	https://folio-org.atlassian.net/browse/ERM-2381
	https://folio-org.atlassian.net/browse/ERM-2383
	https://folio-org.atlassian.net/browse/ERM-2385
	https://folio-org.atlassian.net/browse/ERM-2190		Cannot reproduce. Removed by reporter.
	https://folio-org.atlassian.net/browse/ERM-2261
	https://folio-org.atlassian.net/browse/ERM-2262
	https://folio-org.atlassian.net/browse/ERM-2386

ERM Sprint 150