ERM Sprint 187

Sprint Goal / Focus 

  • 22 Mar: Module Release Deadline

Sprint Schedule

  • Sprint: 187
  • Release: 2024.1 Quesnalia 
    • Sprint 11 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 6 Mar - dev update
  • Mon 11 Mar - backlog review
  • Wed 13 Mar - dev update

Sprint Capacity

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

Carried Over

ERM-3164 - Getting issue details... STATUS (plus)

ERM-3163 - Getting issue details... STATUS (plus)

ERM-1908 - Getting issue details... STATUS (plus) Claudia Malzer

ERM-3162 - Getting issue details... STATUS


ERM-3161 - Getting issue details... STATUS

TBC

  • Fix error
  • Consider additional logging that may be needed to elaborate "

    problem processing remote KB link"


ERM-3139 - Getting issue details... STATUS


ERM-3048 - Getting issue details... STATUS (tick) 
  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 
  • Development Estimate


ERM-1910 - Getting issue details... STATUS


TESTRAILS

Sprint 180

ERM-3133 - Getting issue details... STATUS
TESTRAILSSprint 182
ERM-3130 - Getting issue details... STATUS Monireh Rasouli

 

  • Error locally (but not snapshot): 
    • > Cannot read properties if undefined (reading 'setDefault')
  • From: ui-plugin-find-po-lines: useFetchOrderLines / findRecordsModal
  • Need to work out whether it's our use of it 
  • Could be a moment version mismatch

 

  • updated moment locally (not in package.json of app), which fixed previous issue
  • TODO: debug cause of issue
Sprint 182
ERM-3150 - Getting issue details... STATUS  Jack Golding

Environment set up 

Ready to progress

To follow ERM-3131

 

  • TODO: 
    • check if this is used elsewhere in the app
    • when should this run and where to get best fit
    • where should we store the lastRun timestamp?
      • in memory: lost when instance restarts
      • field on the package? 
  • Out of scope
    • non-UI solution
    • extensive metadata

 

  • Progress
    • added resource count and timestamp to data model
  • TODO
    • may need to update timestamp

ERM-3131 - Getting issue details... STATUS Jack Golding

 

  • Not currently able to reproduce in an Orchid environment
  • TODO: rebuild Orchid with fresh rancher setup

ERM-3156 - Getting issue details... STATUS Ethan Freestone

Next up ... 

  • TODO: 
    • load onto a branch
    • test
    • prepare for release
  • CSP

ERM-3041 - Getting issue details... STATUS

Claudia Malzer

Ethan Freestone

Progress: 

  • Description not shown in Edit
  • No related console errors
  • Same even without changes made

   

TODO:

  • Add log debug
  • Check libraries that are using focus logic
  • look into when states are changed
  • memo-ise line 49 in React useCallback
  • pull line 48 out into another React useCallback

 

  • Changes not been successful
  • Push latest wip SEC and ui-dashboard branches
  • Review after lunch with Ethan

 

  • pulled back in as resolved
  • swapped implementation to import form directly and then render logic handling hook
  • component and hook in place in SEC
  • implemented in dashboard/widgets

ERM-3147 - Getting issue details... STATUS (question)

 

  • Currently does not seem to be a candidate for Poppy CSP, Quesnalia or a backport to Orchid
  • Need to determine what approach we might take to provide case insensitive sorting

ERM-1796 - Getting issue details... STATUS (plus) Ethan Freestone

 

TODO: Needs code review

 

  • Needs some followup with Steve

Grails Track

 

  • Success with compiling and running with Grails 6
  • However, JobRunner is not behaving as expected: 
    • unchanged between 5 and 6 
    • but jobs are not being picked up
    • probably an unnecessary transaction that has been added and is now scoped

 

  • JobRunner triage indicates some client level tasks need tenant scope
    • These can fail silently
  • TODO:
    • diagnose cause of JobRunner fail
    • review areas where this may similarly occur (is this a job issue or pattern issue)
  • UNKNOWN
    • whether this affects beyond mod-0agreements: unlikely as it is related to federation interface with database

 

  • Running out of resources when running harvest on local branch
  • Not reproduced on master, so using that with postgres to get some perfomance data to compare

 

  • mod-agreements
    • compiles, builds, run
    • harvest begins, but goes from 20% CPU usage to 30-90 before climbing to 1005%
  • could be a local laptop issue
  • dev note: set up new application.yaml for an isolated pg/kafka environment to test performance 



  • ERM-3111 - Getting issue details... STATUS
  • ERM-3089 - Getting issue details... STATUS
  • SI-34 - Getting issue details... STATUS
  • SI-38 - Getting issue details... STATUS
  • ERM-3090 - Getting issue details... STATUS


Tests

(minus) Cypress test development stalled pending implementation of STCOR-484 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions





Release Tasks (
Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




Release Tasks (Quesnalia)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA

Release Tasks (Poppy Bug Fix)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA






Sprint Summary

ERM


key summary type assignee status components
Loading...
Refresh

Dashboard

key summary type assignee status components
Loading...
Refresh

Other

key summary type assignee status components labels
Loading...
Refresh

No Label

key summary type assignee status components
Loading...
Refresh