Skip to end of banner
Go to start of banner

2023-06-21 ERM Weekly Delivery Update

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Meeting Details

Date
 
Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously2023-06-14 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities



WIP 

 In Progress
  • ISSUE: 
    • Progress / Impediments: 
    • TODO: 
    • New unknowns: 
    • Help or input needed: 
    • ETA for review: 
  • What progress or impediment on previously stated actions?
  • What's left to do?
  • Any new unknowns?
  • What help or input is needed?
  • When expected to be ready for review?

In Progress

  • ERM-2937 - Getting issue details... STATUS
    • Progress / Impediments: 
    • TODO: 
      • need to double check our implementation and see if we can get this working without the labelling
      • then revert to JC / #stripes 
      • need to reconcile inconsistency of pagination across FOLIO apps, and anti-pattern of importing from acquisitions
    • New unknowns / Help or input needed:  NA
    • ETA for review: NA
  • ERM-2421 - Getting issue details... STATUS
    • moved to code review
  • ERM-2934 - Getting issue details... STATUS

Pending

 Blocked
  • ISSUE
    • Blocking conditions
    • Action needed
  • Are the blocking conditions still relevant? 
  • What action is needed to unblock, and by whom?


 Needs Elaboration
  • ISSUE: 
    • Who / When: 
    • ETA Ready for Dev: 
  • Who needs to be involved in the elaboration process? 
  • What is the timeframe for getting input?
  • When is the issue expected to be ready for development?


 Sprint Backlog


  • Who is picking up what next?
  • When is next issue expected to start / complete?
  • Anything needed to start next issue (dependencies or clarifications)?

Blocked

  • ERM-2923 - Getting issue details... STATUS / ERM-2939 - Getting issue details... STATUS
    • Progress/Impediments:
      • required bubbling hierarchy update, which is tricky with Grails save handling of save
      • identified what appeared to be a non-standard double-saving code block that has been moved to event listener - appeared to work, but broke ingest when merged
      • currently only bubbles 1 step up or down, rather than full tree
      • last updated increasingly proving to be the wrong field for this
    • TODO:
      • merge frontend changes for ERM-2923
      • revert changes in listener from ERM-2939
      • then review what the goal for coverage and last updated and re-engineer an appropriate solution as part of UXPROD-4272 & UXPROD-4271 (Owen) and review with team+Steve
    • New unknowns / help or input needed: NA
    • ETA for review: today

Needs Elaboration / Triage

  • NA

Sprint Backlog - Next Up

  • NA

Allocations

  • Claudia: 
    • ERM-2922 - Getting issue details... STATUS
      • options
        • maybe decouple search from SAS so it goes into the url and then fill the box from the url? 
  • Ethan: 
  • Jack: 
    • ERM-2421 - Getting issue details... STATUS
      • returned to dev for e2e testing
    • ERM-2934 - Getting issue details... STATUS
      • enum and display column changes made 
      • need labels adding
    • ERM-1110 - Getting issue details... STATUS

At Risk

  • What is now at risk of not being started this sprint?
  • Do any of these take priority over other sprint backlog items?

Sprint Backlog - to follow

Sprint Backlog -  At Risk

  • NA

Removed

  • NA

In Review

  • Any impediments to review or QA?
  • Any useful context, implementation choices or limitations for the reviewer/tester to know ?


Code Review:

  • NA

QA / UAT 

  • ERM-2641 - Getting issue details... STATUS
  • SI-23 - Getting issue details... STATUS

Release Candidates

  • What has passed QA since last dev call?
  • What has been closed since last dev call?

For Release / Awaiting Deployment

  • ERM-2929 - Getting issue details... STATUS
    • awaiting Nolana (ERM-2932) environments rebuild for testing 
    • raised to Oleksii for action

Pending Testrails

  • NA


Closed: Nolana CSP

  • NA


Closed: Orchid CSP

  • NA


Closed: Poppy R2023.2

Stories / Bugs

Maintenance / Tasks

  • NA

Release Tasks

Closed (No ERM Release)

  • NA
  • <10 mins

AOB


New Issues

  • ERM-2941 - Getting issue details... STATUS / ERM-2942 - Getting issue details... STATUS
    • undergoing triage by k-int
    • Slack conversation group
    • possibly related to reference environment build issues 
    • Raised as P2 - not really clear why

Added to sprint

  • NA

Not added to sprint

  • NA

Other

  • NA

Component Updates

  • NA

Release Planning

  • NA

Testing

Security

  • No labels