ERM Sprint 179

ERM Sprint 179

Sprint Goal / Focus 

  •  

Sprint Schedule

  • Sprint: 177

  • Release: 2023.2 Poppy 

  •  

    • Sprint ???: Bugfix Release Deadline (---) [FOLREL-581]

  • Release: 2024.1 Quesnalia 

    • Sprint 4 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

  • Wed 22 Nov

  • Mon 27 Nov

  • Wed 29 Nov

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

Lead Roles:

  • Code Review: @Ethan Freestone 

  • QA:  @Owen Stephens 

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present

  • @Jag Goraya 

  • @Ethan Freestone 

  • @Owen Stephens 

  • @Claudia Malzer 

  • @Jack Golding 

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

@Claudia Malzer 

  • Approach

    • Remove picklist values pane

    • Add 'open' state to manage picklists view

    • Bring existing component being rendered into fourth pane

      • add new component to avoid conflict with editable refdata list

    • Adjust to make presentable

    • No need for search and sort style routing, backend filtering or cyclic linking

  • Components and Changes

    • Frontend:

      • stripes-kint-components (editable refdata category list)

      • ui-licenses

    • Backend: none

  • Tests / Data / Dependencies

    • new SKC tests

    • tweak to licenses tests to render new thing

  • Known Unknowns: NA

  • QA: snapshot 

  • Release Target: Quesnalia

  • Development Estimate 

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

  • Approach

    • set or unset refdata category

    • needs migration

      • look for and plug missing context 

      • change categoryId

      • add foreign key constraint migration

  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements

  • Tests / Data / Dependencies: NA

  • Known Unknowns: NA

  • QA: snapshot

  • Release Target:  Quesnalia

  • Development Estimate

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

Ethan or Jack

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target:  Quesnalia

  • Development Estimate: <2 day

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

@Claudia Malzer @Monireh Rasouli 

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia

  • Development Estimate: 

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

@Monireh Rasouli 

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: Quesnalia

  • Development Estimate: 

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

 

  • Pending release decision on SI-38 for grails-okapi

  • Revisit in Sprint 180

  • Release Target: Quesnalia

Tests

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

@Claudia Malzer 




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

@Ethan Freestone 

TBC whether this needs to be applied to Poppy as well as Quesnalia.

Depends on when refresh token rotation is introduced.

Release Tasks (Orchid CSP)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

@Ethan Freestone 



Release Tasks (Poppy Bug Fix)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

@Ethan Freestone 



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

@Ethan Freestone 



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

@Ethan Freestone 



Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

@Ethan Freestone 





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/SI-34

  • Pending release decision on SI-38 for grails-okapi

  • Revisit in Sprint 180

  • Release Target: Quesnalia



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

@Jack Golding  

  • Current State

  • TODO

    • Adding final tests

  • Development Estimate: Monday



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

@Jack Golding 

  • Current State

    • attempting to work out queries

  • TODO

    • index migration testing

  • Development Estimate: Wednesday



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

@Ethan Freestone 

  • Current State

    • code changes done

    • waiting on grails-okapi

    • effectively waiting on SI-38 being releaseable

  • TODO

    • nothing

  • Development Estimate



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

  @Monireh Rasouli 













Sprint Backlog

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

@Ethan Freestone 

  • Approach

  •  

    • set up new open source project in K-Int gitlab

    • new micronaut service required (not using okapi or grails)

    • set up a test instance

    • will need a different dev workflow (probably using local copy of service)

    • working title: pushkb

    • avoid storing caches of transient data

  • Components and Changes

    • Frontend: na

    • Backend: new

  • Tests / Data / Dependencies

    • Align to when GBV start testing and using pushkb endpoint

    • ERM-3048 Possible package schema changes  with endpoint changes

  • Known Unknowns

    • should be (but not clear yet) about TitleInstance Resolver

    • packageSchemaUpdater: potential conflicts when there are multiple copies of schemas in play where backwards compatibility is broken

  • QA: snapshot | local | testing | other

  • Release Target:  Quesnalia

  • Development Estimate