2023-05-03 ERM Weekly Delivery Update

Meeting Details


11:30am UK, 12:30pm Germany


Video Call in

Previously2023-04-26 ERM Weekly Delivery Update
ReferencesJIRA Issue Board



  • Claudia

Discussion items




<5 minsIntroductions

Call Priorities

ERM-2631 - Getting issue details... STATUS

  • Assigned to Owen to update with summary from conversation notes


 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: 
      • SI done and looks good
      • Licenses running, migrations and endpoints working
      • Licenses tests failing
        • logback files changed from groovy to xml, which is conflicting in licenses (though not others)
    • TODO: 
      • Licenses tests
      • Agreements
      • Steve > release, docker 
    • New unknowns: NA
    • Help or input needed: Steve for release/docker
    • ETA for review: aim for mod-si by end of week
  • ERM-2790 - Getting issue details... STATUS
    • Progress / Impediments: 
      • initial version published
    • TODO: NA
    • New unknowns / Help or input needed: NA
    • ETA for review: now
  •   ERM-2773 - Getting issue details... STATUS  
    • Progress / Impediments: 
      • could create user with password and permissions based on stripes-testing example
      • code example is more than needed, and does require UI
    • TODO: 
      • attempt to simplify stripes-testing example code down for ERM purposes
      • investigate file upload
      • remainder of test script required
    • New unknowns / Help or input needed: NA, beyond existing investigating
    • ETA for review: unknown


    • 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)?


  • NA

Needs Elaboration / Triage

  • NA

Sprint Backlog - Next Up

  • ERM-1061 - Getting issue details... STATUS
    • To hide Load All when everything is loaded


  • Claudia: NA
  • Ethan: 
  • Jack: 

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

In Review

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

Code Review:

  • NA


  • ERM-2907 - Getting issue details... STATUS
  • ERM-2913 - Getting issue details... STATUS
  • ERM-2918 - Getting issue details... STATUS
    • to review with Annika if this is used/needed still with eUsage

Release Candidates

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

For Release 

Pending Testrails

  • NA

Closed: Nolana Hot Fix

Closed: Poppy R2023.2

Stories / Bugs

Maintenance / Tasks

  • NA

Release Tasks

Closed (No ERM Release)

  • <10 mins


New Issues

Added to sprint

  • NA

Not added to sprint

  • NA


  • NA

Component Updates

  • NA

Release Planning