/
2023-10-11 ERM Weekly Delivery Update

2023-10-11 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Oct 11, 2023

Meeting Details

Date
 
Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously2023-10-04 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

  • Ethan

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • Potential issue with mod-service-interaction release, where module descriptor isn't updated

WIP 

 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-2836 - Getting issue details... STATUS
    • Progress / Impediments: 
      • looking to extend ERM-2841 tests, which needs to do an import
      • intermittent failures still on ERM-2841
    • TODO: 
      • need to temporarily set tenant timezone to UTC to avoid mistimed record creation/check
        • Claudia to update cypress tests for timezone check and persistentJobStatus (as with for agreementStatus: candidate for generalising so it can be used with other refdata)
      • Ethan to attempt to reproduce and triage 
    • New unknowns: 
      • inconsistent failures across clients against shared environments
    • Help or input needed: 
      • test doesn't pass fully for Monireh
      • if cypress test needs to import, job queue must be clear, so will fail if ingest/harvest is in progress
    • ETA for review: 

Pending

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

Blocked

  • NA

Needs Elaboration / Triage

  • NA

Sprint Backlog - Next Up

Allocations

  • Claudia:
  • Ethan: SKC review and release
  • Jack: Release Tasks
  • Monireh: TBD has/not filter use cases



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

  • Release Tasks 

Sprint Backlog -  At Risk

  • NA

Removed

  • NA

In Review

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


Code Review:

QA / UAT 


Release Candidates

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

For Release / Awaiting Deployment

  • ERM-3018 - Getting issue details... STATUS  
    • release notes required

Pending Testrails


Closed: Poppy R2023.2

Stories / Bugs

Maintenance / Tasks

  • NA

Release Tasks

Closed (No ERM Release)

Testing Tasks

  • NA
  • <10 mins

AOB


New Issues

  • NA

Added to sprint

Not added to sprint

Other

  • NA

Component Updates

  • NA

Release Planning

  • NA

Testing

Security