Child pages
  • 2022-02-02 ERM Weekly Delivery Update
Skip to end of metadata
Go to start of metadata

Meeting Details




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


Video Call in

Previously2022-01-26 ERM Weekly Delivery Update
ReferencesJIRA Issue Board



Discussion items




<5 minsIntroductions

Call Priorities


  • 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-1953 - Getting issue details... STATUS
    • Resolved and merged
    • Ready for QA
  • ERM-1958 - Getting issue details... STATUS
    • missing new dashboard option
    • rebuilding vagrant 
    • will need to manually assign permissions
  • ERM-1744 - Getting issue details... STATUS
    • Just started



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

Needs Elaboration

  • 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

  • NA

Sprint Backlog - Next Up

  • Claudia:
  • Ethan:
    • ERM-1800 - Getting issue details... STATUS
      • further requirement analysis needed by Owen
        • will need to be revisited once 1799 changes are made
      • needs ERM-1799 and backend for 1986 to be complete before 
  • Monireh: 
    •  / ERM-1745 - Getting issue details... STATUS
  • Peter:  TBD

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-1938 - Getting issue details... STATUS  
  • ERM-1981 - Getting issue details... STATUS
    • needs input from Ian Ibbotson 
    • issue table delivered, but description effect not happening 

Sprint Backlog -  At Risk

  • ERM-1990 - Getting issue details... STATUS
  • ERM-1923 - Getting issue details... STATUS  
    • comment to be added
    • looks like start and end date are double handled causing technically bad json
    • should be starightforward, but some complexity as transient
  • ERM-1920 - Getting issue details... STATUS
    • options: either strip out the code or exception handle 
    • decision: closing and dealing with by exception

In Review

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

Code Review: 

  • ERM-1980 - Getting issue details... STATUS
    • need to still add CODEOWNERS
    • reassigned to Monireh to comment out tests and resubmit PR


  • ERM-1799 - Getting issue details... STATUS
    • now has a job to fire to backfill assign match keys
      • not intending to be used more than once
      • restricted to admin
    • likely to need more work
  • ERM-1986 - Getting issue details... STATUS
    • backend amends needed for 
    • frontend designs complete, to implement after 1800

Bugfix Cycle 

  • NA

Release Candidates

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



  • NA

Closed: Lotus R1 2022


RTL / Other Tests

  • NA
<10 mins


New Issues

Added to sprint

  • NA

Not added to sprint

  • NA


  •  NA