2023-09-20 ERM Weekly Delivery Update

Meeting Details

Date
Ā 
Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously2023-09-13 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities

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:Ā 
  • ERM-2983 - Getting issue details... STATUS
    • Progress / Impediments:Ā 
      • reusing some work from OA
      • making good progress alongside 3010
    • ETA for review: Friday
  • ERM-3010 - Getting issue details... STATUS
    • Progress / Impediments:Ā 
      • spoke about implementing grouping changes - not resolved
      • parser for query groups implemented and tested successfully
      • validation for not completed
    • TODO:Ā 
      • related agreements
    • New unknowns: NA
    • Help or input needed:Ā 
      • do we treat related agreements as separate inward/outward entities or as a single relationship? single
    • ETA for review: Wednesday
  • ERM-3018 - Getting issue details... STATUS
    • Progress / Impediments:Ā 
      • code written
      • run comparative near full ingests that appear to work well
    • TODO:Ā 
      • check sibling logic
      • test individual scenarios
      • set up temporary endpoint for domain creation to enable testable scenarios
    • New unknowns: NA
    • Help or input needed:Ā 
      • need individual test cases and imports fleshing out
        • OS to progress today
    • ETA for review:Ā 
  • ERM-3040 - Getting issue details... STATUS
    • Progress / Impediments:
      • picked up and fixed
      • PR raised now
    • TODO:Ā 
      • set smaller fixed width for Remove column
      • revert styling changes in PR
    • ETA for review: now

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: NA
  • Jack: NA
  • Monireh: 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

  • NAĀ 

Sprint Backlog -Ā  At Risk

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:

  • ERM-2992 - Getting issue details... STATUS
  • ERM-3038 - Getting issue details... STATUS
    • not ideal, but the fix resolves the issue
    • some adjustments being made to initial values
    • but effectively same approach
  • ERM-3024 - Getting issue details... STATUS

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-1795 - Getting issue details... STATUS
  • ERM-2979 - Getting issue details... STATUS
  • ERM-2993 - Getting issue details... STATUS
  • SI-24 - Getting issue details... STATUS
  • ERM-3013 - Getting issue details... STATUS
  • ERM-3014 - Getting issue details... STATUS

Pending Testrails


Closed: Poppy R2023.2

Stories / Bugs

Maintenance / Tasks

  • Node update in GitHub Actions

Release Tasks

Closed (No ERM Release)

Testing Tasks

  • NA
  • <10 mins

AOB


New Issues

Added to sprint

Not added to sprint

  • ERM-3041 - Getting issue details... STATUS
    • previously used stripes-final-form
    • implementation needs to become reusable patternĀ 

Other

  • NA

Component Updates

  • NA

Release Planning

  • NA

Testing

Security