2023-02-15 ERM Weekly Delivery Update

Meeting Details


11:30am UK, 12:30pm Germany


Video Call in

Previously2023-02-01 ERM Weekly Delivery Update
ReferencesJIRA Issue Board



Discussion items




<5 minsIntroductions

Call Priorities
  • Added change to SKC to strip out diacritics and special characters to ease internationalisation
  • Add test to stripes-kint-components to check encoding of special characters
  • ERM-2612 - Getting issue details... STATUS
    • JC has added an onAdd prop and a story to the stripes storybook, pending merge
    • EF and MR to schedule a call to work through and feedback on branch
  • ERM-2624 - Getting issue details... STATUS / ERM-2625 - Getting issue details... STATUS


 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-2633 - Getting issue details... STATUS
    • Progress / Impediments: 
      • Started today
      • Error when cancelling New Proxy Server workflow
        • Looks like null values with empty array
      • Need to find actions menu
    • TODO: 
      • Fix error on cancel
      • Test using local proxy server
    • New unknowns: 
    • Help or input needed:  
    • ETA for review: Next week
  • ERM-2629 - Getting issue details... STATUS
    • Progress / Impediments: 
      • draft pr raised
      • waiting for build to come through
        • corrupted key file looks like the issue
      • checked with local backend
      • reviewed and approved on call
    • TODO: 
      • check restart: backend with old mod-agreements and json file, add widget, start backend
    • New unknowns / Help or input needed: NA
    • ETA for review: depends on build


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


  • ERM-2612 - Getting issue details... STATUS
    • Attempting to implement fix that John developed, but still not working as a result of possible race condition when deleting
    • Possible final-form <> redux-form conversion conflict
    • Not a great solution ... possibly too complex for specific needs
    • Redefine issue to separately
      • avoid multiselect for this use case
      • improve multiselect pattern for other scenario
    • TODO:
      • Close current frontend branches and PR
      • Add Jira to either create multiselection component
      • Use kiwtFieldArray with add/remove

Needs Elaboration / Triage

Sprint Backlog - Next Up

  • ERM-2433 - Getting issue details... STATUS
    • compiled locally
    • waiting for PRs to build, once maven issue is resolve
    • Add issue for hibernate, gorm, grails need updating
  • ERM-2630 - Getting issue details... STATUS
  • ERM-2506 - Getting issue details... STATUS
  • ERM-2634 - Getting issue details... STATUS


  • Claudia: 
    • set up new issue for LKB new proxy cancel issue
  • Ethan: 
    • ERM-2612
    • Releases
    • ERM-2630 - Getting issue details... STATUS
  • Monireh: 
    • ERM-2612 frontend
    • ERM-2634 - Getting issue details... STATUS

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:

  • ERM-2632 - Getting issue details... STATUS
  • ERM-2624 - Getting issue details... STATUS / ERM-2625 - Getting issue details... STATUS
    • Using settings.[agreements].enabled
    • Does lose individual screen access permission granularity, which may give access to more than they currently have
    • Actions: 
      • Close PRs (CM/EF)
      • Feedback to reporter (OS)
      • Set up technical options discussion with CM, EF, OS, MJ (JG)
      • Review overall intended permissions against existing configuration (OS)
    • Note: design goal: be able to check against single permissions 


Release Candidates

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

For Release / Pending Testrails

Closed: Orchid R2023.1

Stories / Bugs

RTL / Tasks

  • NA

Closed (No ERM Release)

  • <10 mins


New Issues

Added to sprint

Not added to sprint

  • NA


Component Updates

  • NA

Release Planning

  • K-int Maven down. Merge and Release to backend is down



  • NA