ERM Sprint 159

ERM Sprint 159

Sprint Goal / Focus 

Sprint Schedule

  • Sprint: 159

  • Release: 2023.1 Orchid  

    • Sprint 8 of 8 since Release Development Cycle Starts (Sprint 151) to Feature Freeze (Sprint 158)

    • Sprint 159: Module Release Deadline [FOLREL-565]

      • Backend 22 Feb 2023

      • Frontend 24 Feb 2023

    • Sprint 162: Bugfix Release Deadline (31 Mar 2023) [FOLREL-581]

  • Release: 2023.2 Poppy  

    • Sprint 1 of 7 since Release Development Cycle Starts (Sprint 159) to Feature Freeze (Sprint 166)

    • Sprint 168: Module Release Deadline (16 Jun 2023) [FOLREL-565]

    • Sprint 170: Bugfix Release Deadline (21 Jul 2023) [FOLREL-581]

Development Meetings

Sprint Capacity

Team AvailabilitySchedule | 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 

  • @Monireh Rasouli 

  • @Claudia Malzer

  • @Owen Stephens 

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 Capacity

  3. Review sprint candidates 

  4. Agree technical approach / define key implementation tasks

  5. Finalise estimates / costings

  6. Confirm sprint scope

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

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

@Ethan Freestone 

  • Approach

    • Add a new synchronous endpoint to receive list of TIPP data

    • Add service logic to handle endpoint

    • TIPP-based, so supports limited number

    • Retry if not returned OK

    • Package reconciliation

  • Components and Changes

    • Frontend

    • Backend: mod-agreements

  • Tests / Data / Dependencies

  • Known Unknowns

    • what is a good limit? start with 5000, but depends on performance, esp

      • http request rate limits

      • okapi handling

    • will this go outside of the existing job process? 

      • yes

      • will be slower, but won't need a reset cursor

    • Storing title/package data to reconcile

    • what is the shape of data to ingest

  • QA: snapshot | local | testing | other

  • Release Target: Poppy

  • Development Estimate:  6 sprints

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

@Owen Stephens  to elaborate

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

    • Should this use scrolling api or OAI-PMH?

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

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

@Owen Stephens to review 

  • Triage

    • Multiple possible alternative names, so behaviour may still return matches when attempting negation matching, which is consistent with hibernate behaviour

      • uses ALL rather than ANY negative matching

  • Approach

    • likely to be a new operator and widget type (SimpleSearch 1.1)

  • Components and Changes

    • Frontend: ui-dashboard

    • Backend: kint-toolkit, mod-service-interaction, mod-agreements

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate

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

 

@Monireh Rasouli  @Claudia Malzer 

  • Triage

    • Only one description field, so should be same as filter by Agreement

  • Approach

  • Components and Changes

    • Frontend: NA

    • Backend: mod-agreements

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot 

  • Release Target: Poppy

  • Development Estimate: 1d

No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

@Claudia Malzer 

  • Approach

    • Follow pattern as for ERM-2624 and ERM-2625

  • Components and Changes

    • Frontend: ui-local-kb-admin, stripes-erm-components

    • Backend: NA

  • Tests / Data / Dependencies

    • No stripes-kint-components changes expected

    • ERM-2624

  • Known Unknowns: 

    • May need okapi refresh to flush a permission cache?

  • QA: snapshot

  • Release Target: Poppy

  • Development Estimate: 1d

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

@Monireh Rasouli 

  • Approach

    • Implement icon button with copy functionality

    • Add toast notification

    • Alternative: ClipCopy from stripes-components as per POLine

  • Components and Changes

    • Frontend: ui-agreements, ui-licenses

    • Backend: na

  • Tests / Data / Dependencies

  • Known Unknowns: NA

  • QA: snapshot 

  • Release Target: Orchid

  • Development Estimate: 1d

Release Tasks (Orchid)

Backend: 1d

Frontend: 2d

Release Tasks (Morning Glory Hotfix)

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

 

@Ethan Freestone 

Add test to stripes-kint-components to check encoding of special characters

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

@Ethan Freestone 

  1. Set up Jira issue

  2. Set up cypress end-to-end test for agreements (Ethan)

    1. check it exists in navbar, and that it shows up 

    2. work out how to run it

    3. use as template for extending within agreements

  3. Export Testrails list (Owen)

  4. Review for e2e conversion (team)

  5. Get Testrails logins (Jag)

Development Estimate: 2d

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

@Monireh Rasouli 

  • Approach

    • specify limit as 1000

    • make consistent use of ==

    • refactor query parameterisation to use string rather than array, to ensure consistent component types

  • Components and Changes

    • Frontend: stripes-erm-components

    • Backend: NA

  • Tests / Data / Dependencies: NA

  • Known Unknowns: NA

  • QA: snapshot | local | testing | other

  • Release Target: Orchid

  • Development Estimate: <1d

NA

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

@Ethan Freestone 

  •  

  • Release Target: Orchid

 

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