2021-09-22 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Sep 22, 2021
2 min read

Meeting Details

Date

 

Time

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

Location

Video Call in

Previously2021-09-15 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

  • Peter Bohm
  • Claudia Malzer

Discussion items

Time

Item

Notes

<5 minsIntroductions

Previous Actions

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 

  • ERM-1816 - Getting issue details... STATUS
    • not appearing on snapshot
      • testing using mod-agreements 5.0
      • snapshot using mod-agreements 4.2
    • does not appear that there are any other modules with a dependency on an earlier version
    • raised in #hosted-reference-envs
  • ERM-1848 - Getting issue details... STATUS
  • ERM-1697 - Getting issue details... STATUS

Bugfix Cycle 

  • NA



WIP 

  • What progress or impediment on previously stated actions?
  • What's left to do?
  • What help or input is needed?
  • When expected to be ready for review?

In Progress

  • ERM-1798 - Getting issue details... STATUS
    • Code still expected for review on Friday
    • Snag with whitespace and capitalisation - will need a new normalised name field
    • TODO:
      • introduce normaliser to resource table (new and migrtation validation)
        • include normaliser as part of title matching
      • then close to the algorithm that's needed - requires more technical analysis
      • secondary id matching
      • sibling creation 
  • ERM-1258 - Getting issue details... STATUS
    • formEresource
      • cards
      • mobile use
      • coverage fail warning
    • formCoverage in code review

Pending

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

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

Blocked

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

Sprint Backlog - Next Up

  • ERM-1754 - Getting issue details... STATUS
    • integration tests required
    • branch available
    • original dev on leave - at risk for Kiwi release, handed over to Ethan to complete
  • ERM-1863 - Getting issue details... STATUS
  • ERM-1700 - Getting issue details... STATUS
    • this is about bringing in line with other cards, such as package  details on agreement line / package
    • email address will span two columns

Sprint Backlog - to follow

  • ERM-1862 - Getting issue details... STATUS
    • needs to be fixed in stripes-components
    • can be developed but won't be reviewed until John Coburn returns from leave after today and can pick it up
    • still expected to be resolved for Kiwi

Needs Elaboration

  • NA

Blocked

  • 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 

NA


Release Candidates

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

Accepted 

Requiring testrail cases

Closed

<10 mins

AOB


New Issues

Added to sprint

Not added to sprint

Other

  • NA