Child pages
  • 2023-05-24 ERM Weekly Delivery Update
Skip to end of metadata
Go to start of metadata

Meeting Details


11:30am UK, 12:30pm Germany


Video Call in

Previously2023-05-17 ERM Weekly Delivery Update
ReferencesJIRA Issue Board



Discussion items




<5 minsIntroductions

Call Priorities

ERM-2929 - Getting issue details... STATUS

  • priority for back fixes is Nolana then Orchid
  • will need testing guidance for ancillary scenarios identified, as no anomalous behaviour is currently replicable:
This will also impact other areas which use useBatchedFetch, which on tip of master comprises of InternalContactSelection, AgreementLines in agreements SASQ, Agreements in basket, related entitlements in eresource view, linked agreements in license/amendment view, platforms in proxy server settings page, entitlements in package field for erm-comparisons.
  • issue arises from new batch function introduced as part o freact query migration


  • 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: 
      • first attempt to release by Steve this morning
      • blocked by maven
      • otherwise clear to proceed
    • TODO: 
      • Release by Steve (plugins)
      • Release by Ethan (back-end modules)
    • New unknowns: NA
    • Help or input needed: 
      • update needed for documentation? confer with Steve
    • ETA for review: this week
  • ERM-2421 - Getting issue details... STATUS
    • TODO:
      • Moved for Code Review
    • ETA for review: today
  • ERM-2919 - Getting issue details... STATUS
    • Progress / Impediments: 
    • TODO: 
    • New unknowns: 
    • Help or input needed: 
    • ETA for review: 


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

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

  • 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


  • Claudia: 
    • NA
  • Ethan: 
  • Jack: NA

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


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

  • NA

Closed: Poppy R2023.2

Stories / Bugs

Maintenance / Tasks

  • NA

Release Tasks

Closed (No ERM Release)

  • <10 mins


New Issues

  • NA

Added to sprint

Not added to sprint

  • NA


  • NA

Component Updates

  • NA

Release Planning