2022-08-24 ERM Weekly Delivery Update

Meeting Details




9:05am ET, 2:05pm UK, 3:05pm Germany


Video Call in

Previously2022-08-17 ERM Weekly Delivery Update
ReferencesJIRA Issue Board



  • Owen Stephens
  • Monireh Rasouli
  • Gill Osguthorpe

Discussion items




<5 minsIntroductions

Call Priorities


 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-2328 - Getting issue details... STATUS
    • Progress / Impediments: NA
    • TODO: 
      • Not required
      • Closed
  • ERM-2306 - Getting issue details... STATUS
    • Progress / Impediments: 
      • domain class, migrations done
    • TODO: 
      • run tests 
    • New unknowns: NA
    • Help or input needed: NA
    • ETA for review: End of today
  • ERM-2288 - Getting issue details... STATUS
    • Progress / Impediments: 
    • TODO: 
      • iterate first over the current attributes to check if included in the first 
      • if not, remove each separately
      • iterate over new list being ingested, and check for attribute presence, and remove if not
      • complete as a single transaction (should already be in place, as saving at the end)
      • potentially add a compare list routine to reuse code (not expected)
    • New unknowns: NA
    • Help or input needed:
      • work out how to do it in Groovy with different data types
    • ETA for review: Thu/Mon


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


Needs Elaboration

  • ERM-2314 - Getting issue details... STATUS  
    • Who / When: 
    • ETA Ready for Dev: 

Sprint Backlog - Next Up

  • Claudia:  
    • ERM-2315 - Getting issue details... STATUS
      • extend getResourceIdentifier() with a returnAll boolean parameter (stripes-erm-components)
        • use this to determine whether to return a list or single identifier
        • set to true when using on this screen
      • tweak test for getResourceIdentifier
      • update ui-agreements to apply logic
      • add tests to eResourceIdentifier to check multiple cases
      • add unique key to array list entries for react to handle correctly
      • in eResourceIdentifier, 
        • assume always true
        • render list using stripes-list component
  • Ethan: 
  • Monireh:  NA
  • Peter:

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-2214 - Getting issue details... STATUS
    • relates to translations that are coming from kint-components
    • therefore related to and being handled as part of migration of kint-components ( ERM-2316 - Getting issue details... STATUS )

Sprint Backlog -  At Risk

In Review

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

Code Review:

  • NA 


Bugfix Cycle 

  • NA

Release Candidates

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


  • NA

Closed: Nolana R2022.3

Stories / Bugs

  • NA

RTL / Tasks

Closed (No ERM Release)

  • <10 mins


New Issues

Added to sprint

  • NA

Not added to sprint

  • NA


  • mod-service-interaction and ui-dashboard will need the breaking changes from ERM-2312 to work in development environments.
  • ui-agreements has breaking changes from ERM-2289
    • new example of a single component with two separate url routes to access
    • new changes check request origin to make sure that user is returned to the correct place afterwards
  • Vagrant box is deprecated