2022-08-10 ERM Weekly Delivery Update

Meeting Details




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


Video Call in

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



  • Claudia Malzer
  • Monireh Rasouli

Discussion items




<5 minsIntroductions

Call Priorities
  • ERM-2305 - Getting issue details... STATUS
    • Rescheduled for MG BugFix (see Slack note)
    • Needs to be deployed by Fri 12 Aug
    • Expected by Thursday


 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-2289 - Getting issue details... STATUS
    • Progress / Impediments:
      • Tests written for components
    • TODO: 
      • Fix POLine filter
      • Implement review changes (such as agreementLines url)
    • New unknowns: NA
    • Help or input needed: NA
    • ETA for review: Fri/Mon
  • ERM-2288 - Getting issue details... STATUS
    • Progress / Impediments: 
      • vagrant box issues (resolved)
      • more fields being updated now
      • no new service required
    • TODO: 
      • many-to-many fields not working (alt resource name, content type) 
        • looks right,
        • need to debug each package line
      • Test Kbart, GOkb Import
    • New unknowns: NA
    • Help or input needed:
      • GOkb account
      • confirmed also to update `alternateResourceNames`
    • ETA for review:  Thursday
  • ERM-2312 - Getting issue details... STATUS
    • Progress / Impediments: 
      • just started to write up domain class
    • TODO: all of it
    • New unknowns: 
      • migrations expecting to be quite tricky
    • Help or input needed: NA
    • ETA for review: Sprint 147


    • 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-2311 - Getting issue details... STATUS - readied.
  • ERM-2313 - Getting issue details... STATUS
    • Gill to provide wireframes
    • Need some sense of API shape (ERM-2312)
  • ERM-2314 - Getting issue details... STATUS  
    • to follow Owen's return from Wolfcon
    • to also include editing name
      • will need to refactor routing (currently based on name)

Sprint Backlog - Next Up

  • Claudia:  TBC
  • Ethan: 
  • Monireh:  
  • 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

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 

Release Candidates

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


  • NA

Closed: Morning Glory R2022.2

Stories / Bugs

Closed: Morning Glory Big Fix R2022.2

Stories / Bugs

  • NA


  • NA

Closed: Nolana R2022.3

Stories / Bugs

RTL / Tasks

Closed (No ERM Release)

  • NA
  • <10 mins


New Issues

Added to sprint

Not added to sprint

  • NA


  • Re ERM-2289
    • Button grouping to be reviewed at next SIG 10 Aug
      • changes expected
      • boiled down to two options
        1. collapsing tab group (would require new component)
        2. new (parent) tab group 
      • group has until Monday to review
    • Gill to raise new issue once confirmed