2022-11-02 ERM Weekly Delivery Update

Meeting Details




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


Video Call in

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



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-2405 - Getting issue details... STATUS
    • Pending 
  • ERM-2261 - Getting issue details... STATUS
    • Progress / Impediments: 
      • Finished - tests passing
      • Needs to test for licensor / primary org
    • ETA for review: Thursday


    • 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

  • NA

Sprint Backlog - Next Up

  • RTL: ui-plugin-find-eresource


  • Claudia: RTL: ui-plugin-find-license
  • Ethan: 
    • ERM-2331 - Getting issue details... STATUS
      • doing some followup work to check that proposed way forward is viable
    • ERM-2414 - Getting issue details... STATUS
  • 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

  • NA

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:


Waiting for snapshot to rebuild

Bugfix Cycle 

  • NA

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 R2022.3

Stories / Bugs

RTL / Tasks

  • NA

Release Tasks

Closed (No ERM Release)

  • <10 mins



New Issues

Added to sprint

  • ERM-2420 - Getting issue details... STATUS
    • All amendments shown as not set, even if organization set
    • Works by adding roles to path
    • May be a result of change to how organizations work, allowing institutions to define their own roles
    • Therefore started to use primary org instead of licensor role
    • Therefore fix needs to show primary org
    • Change licensor to primary org

Not added to sprint

  • NA


  • Editing agreements with hundreds of agreement lines
    • raised in SIG today
    • OS and GO to confer on req/ux/ui

Component Updates

  • NA

Release Planning

  • stripes-erm-components 7.0.2 released, marked for Nolana Bugfix


  • phased approach identified, and being reviewed to move to shared stripes-erm-testing, prioritising fix to prevent breaking dependency on SEC for builds

Orchid Plans