ERM Sprint 182

ERM Sprint 182

Sprint Goal / Focus 

  •  

Sprint Schedule

  • Sprint: 182

  • Release: 2024.1 Quesnalia 

    • Sprint 7 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 10 Jan 

  • Wed 17 Dec

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 

  • @Claudia Malzer 

  • @Owen Stephens 

  • @Ethan Freestone

  • @Jack Golding

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

@Claudia Malzer 

  • Approach

    • need to include a header from FOLIO

    • can grab tenant from, eg, mod-service-interactor

  • Components and Changes

    • Frontend: NA

    • Backend: mod-agreements or web-toolkit

  • Tests / Data / Dependencies

  • Known Unknowns

    • where to add the header

  • QA: snapshot 

  • Release Target: Quesnelia 

  • Development Estimate: <1d

 

17 Jan:

  • descope version

  • logging

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

@Ethan Freestone 

Triage

Current: 

  • upgrade path documentation doesn't help

  • looks like (via grep) this is the only use of ehcache

TODO

  • need to decide whether to bail ehcache to use another NamedFactory provider

  • potentially could do this internally, without another dependency

  • run gradle clean  and check dependencies to see if ehcache/jetty-io are brought in transitively

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

@Owen Stephens 

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate

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

@Claudia Malzer 

  • Triage

  • Approach

    • Should be able to just turn off autofocus on the end-date

    • However, this is handled by inputRef being on both start and end date, so just get rid of the inputRed on end-date (line 136)

  • Components and Changes

    • Frontend: ui-agreemeents

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate

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

@Owen Stephens 

  • Triage

    • fetch of loadMore is causing cache of what's opened to refresh

    • which may be because of batch fetching PO lines 

    • redraw closes and remounts 

  • Approach

    • needs investigation to understand chain of events leading to invalidation or refresh - what's the trigger

    • then need to decide what's desirable behaviour - do we need to retain the user's view or reset it post-redraw?

      • if we don't then any data changes won't be reflected

    • Owen to revisit whether this is an issue in current versions 

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate

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

@Ethan Freestone 

  • Triage

    • previously created new Grails 6 project and incrementally added components

    • once pitfalls identified, each module took very little time

  • Approach

    • will starting up a new grails project with the CLI even work?

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

    • gradle upgrade is necessary

  • Known Unknowns

    • will starting up a new grails project with the CLI even work?

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate

  • Current:

    • grails and gradle versions determined

    • web-toolkit passing tests

    • smoother process than 4 to 5, but integration is inevitably 

  • TODO

    • service-interaction failing

    • need to build into okapi environment

      • may need to rebuild rancher, which could be risky at the moment

    • review migrations, but difficult to triage atm

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

@Ethan Freestone 

  • Triage

    • need to revisit what choice we made for Poppy

  • Approach

    • need to check whether Orchid/Poppy have the same vulnerability to determine backport requirement

    • otherwise to be dealt with (for Quesnalia) by Grails 6 upgrade

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate

Tests

Cypress test development stalled pending implementation of https://folio-org.atlassian.net/browse/STCOR-484

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

 

 


Release Tasks (Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

 

 

Release Tasks (Orchid CSP)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA

 

 

Release Tasks (Poppy Bug Fix)

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

NA

 

 

 

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

 

Needs Triage to review whether changes made by Ian will resolve.

 

Add column select functionality to selected MCL cases

Example: ui-orders

Approach: 

  1. investigate whether native stripes component integrates cleanly and easily with ERM applications

  2. apply stripes or bespoke component to selected MCLs

 

 

 

 

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

@steve.osguthorpe 

In Code Review

 

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

@Ethan Freestone 

In Code Review

 

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

@Ethan Freestone 

  • Current State

    • being tested by Jack 

  • TODO

  • Development Estimate

 

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

 

  • Current State

    • pushKb can make a scheduled call (1s, 1h) to Gokb

    • will fetch roughly ~700k TIPPS 

    • Stores these in a local postgres db