/
ERM Sprint 177

ERM Sprint 177

Oct 30, 2023

Sprint Goal / Focus 

  • Bug Fixes 

  • Document filters

Sprint Schedule

  • Sprint: 177

  • Release: 2023.2 Poppy 

    • Sprint 178: Bugfix Release Deadline (10 Nov 2023) [FOLREL-581]

  • Release: 2024.1 Quesnalia 

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

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • Monireh: off 23-27 Oct

  • Jack: off 30 Oct

Lead Roles:

  • Code Review: @Ethan Freestone 

  • QA:  @Owen Stephens 

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present

  • @Jag Goraya 

  • @Jack Golding 

  • @Ethan Freestone 

  • @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

 


No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

@Claudia Malzer 

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

@Ethan Freestone 

  • Triage

  • 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: 

  • Development Estimate

https://folio-org.atlassian.net/browse/SI-34

 

  • Triage

    • needs some work to determine handling options, esp how 

  • Approach

    • surface failing definitions at a module level

    • breaking change to handle error response

  • Components and Changes

    • Frontend

    • Backend: grails-okapi

  • Tests / Data / Dependencies

  • Known Unknowns

    • how do we want the api to work when mix of responses

  • QA: snapshot 

  • Release Target: Quesnalia

  • Development Estimate

Tests

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

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

@Ethan Freestone 

Done 

 

 

 

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

@Ethan Freestone 

 

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

@Ethan Freestone 

 

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

@Ethan Freestone 

 

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

@Ethan Freestone 

 

Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/ERM-2432 / https://folio-org.atlassian.net/browse/ERM-3071

@Ethan Freestone 

 

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

@Jack Golding 

  • Approach

    • grep through column names to identify FK constraints

    • check manually each domain class 

    • add _FK to any missing keys

    • set up migrations

    • use pgadmin

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

    • test running from new that indexes are created  

    • manually check for one of each GIN type and regular index type, add a single manual index that precondition works and index isn't created

  • Known Unknowns: NA

  • QA: snapshot 

  • Release Target: Quesnalia

  • Development Estimate: ??

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

 

 

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

 

 

 

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

 

 

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

@Ethan Freestone 

Code Review

 

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

@Ethan Freestone 

Code Review

 

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

@Ethan Freestone 

Code Review

 

https://folio-org.atlassian.net/browse/ERM-3056 / https://folio-org.atlassian.net/browse/ERM-3057 / https://folio-org.atlassian.net/browse/ERM-3058 / https://folio-org.atlassian.net/browse/ERM-3059

@Claudia Malzer 

ui-licenses tests failing on GitHub

will need stripes-erm-components release for tests to work

needs web-toolkit release to fix the right bug

 

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

@Jack Golding 

  • Current State

    • Steve to do the web-toolkit changes

    • Jack has done the frontend changes

  • TODO

    • Patch releases needed for 

      • web-toolkit-ce (Steve)

      • mod-service-interaction 

      • mod-agreements

      • mod-licenses

      • ui-agreements

  • Development Estimate: ??

 

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

@Monireh Rasouli 

 

Blocked

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA

 

 

 

 

 

 

 

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

@Owen Stephens 

 

 

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

@Owen Stephens 

 

 

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

@Owen Stephens 

 

 

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

 

 

 

 

 

 

 

 

 

Bugfix Cycle

Feature ID

Issue ID

Feature ID

Issue ID