/
2023-04-05 ERM Weekly Delivery Update

2023-04-05 ERM Weekly Delivery Update

Owned by Jag Goraya
Apr 05, 2023

Meeting Details

Date
 
Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously2023-03-22 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-2641 - Getting issue details... STATUS
    • Progress / Impediments: 
    • TODO: 
    • New unknowns: 
    • Help or input needed: 
    • ETA for review: 
  • ERM-1061 - Getting issue details... STATUS
    • Progress / Impediments: 
      • Load All button functioning
      • Jump buttons not working
      • List behaviour / rendering issues
    • TODO: 
      • Fix jump buttons rendering
        • css flexbox space-between
      • Fix jump to top/bottom buttons behaviour
        • act on container rather than document
      • Autosize behaviour not as expected
    • New unknowns: NA
    • Help or input needed: 
      • Reach out to John Coburn to verify expected behaviour of autosize
    • ETA for review: 

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

  • NA

Needs Elaboration / Triage

  • SI-20 - Getting issue details... STATUS

Sprint Backlog - Next Up

  • SI-20 - Getting issue details... STATUS

Allocations

  • Claudia: 
  • Ethan: 

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

  • ERM-2630 - Getting issue details... STATUS
    • Progress / Impediments: 
      •  
    • TODO: 
      • some questions to take to users
        • OS to discuss with GBV
        • Martina to set up call 
        • To take forward separate (out of scope) to ERM-2630
      • align new logging with existing jobs 
      • followed by title ingest refactoring
      • update ERM-2631 with summary from conversation notes
    • New unknowns: NA
    • Help or input needed: 
      • Developer workflow / reset environments (from Ian)
        • further discussion needed about how to implement
        • needed for ERM-2631

Sprint Backlog -  At Risk

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:

QA / UAT 

  • ERM-1026 - Getting issue details... STATUS
  • ERM-2885 - Getting issue details... STATUS
  • SI-12 - Getting issue details... STATUS
    • Returned to dev to add validation on save rather than just execution
    • Aim to release for Orchid Bug Fix with whatever is resolved by close of play today

Release Candidates

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

For Release 

Pending Testrails

Closed: Poppy R2023.2

Stories / Bugs

  • NA

Maintenance / Tasks

  • NA

Release Tasks

Closed: Orchid R2023.1 Bugfix

  • NA

Release Tasks

Closed (No ERM Release)

  • <10 mins

AOB


New Issues

  • NA

Added to sprint

  • NA

Not added to sprint

  • NA

Other

  • Stripes update has led to MCL and other frontend tests failing
    • See Slack conversation
    • Fix identified
    • TBD whether to
      • target fix at broken tests 
      • cascade from top level to all tests ← preferred
  • Holds up all frontend pull requests

Component Updates

  • NA

Release Planning

Testing

Security