ERM Sprint 182

Owned by Jag Goraya
Last updated: Jan 17, 2024

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 Availability: Schedule | Calendar

Notes / Exceptions:

Lead Roles:

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present

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

 Sprint Planning Agenda
  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  

(error) - not in sprint

(tick) or @ - in sprint 

(warning) - not ready

(question) - 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

ERM-3127 - Getting issue details... STATUS

(tick) 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

ERM-3118 - Getting issue details... STATUS

(question) Ethan Freestone 

Triage

    • NamedThreadFactory is used in string templating service
    • out of end-of-life support, so should find a  way to upgrade/remove
  • Approach
    • need to review any documented upgrade path - is there a straightforward path to go from 2 to 3
    • are we vulnerable to the jetty-io vulnerabilty?
      • influences backport requirements (esp Orchid which is on Grails 4)

  • Components and Changes

    • Frontend: NA

    • Backend: 

  • Tests / Data / Dependencies

  • Known Unknowns

    • whether we are affected by virtue of using netty

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate

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

ERM-3131 - Getting issue details... STATUS

Owen Stephens 

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate

ERM-3128 - Getting issue details... STATUS

(tick) 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

ERM-3130 - Getting issue details... STATUS

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