/
2023-02-15 ERM Weekly Delivery Update

2023-02-15 ERM Weekly Delivery Update

Feb 20, 2023

Meeting Details

Date

Feb 15, 2023 

Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously

2023-02-01 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Monireh Rasouli 

  • @Owen Stephens 

  • @Ethan Freestone 

  • @Owen Stephens 

  • @Gill Osguthorpe 

  • @Claudia Malzer 

 

Apologies

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

 

WIP 

  • 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

  • https://folio-org.atlassian.net/browse/ERM-2633

    • 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

  • https://folio-org.atlassian.net/browse/ERM-2629

    • 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

 

Pending

  • ISSUE

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

Blocked

  • https://folio-org.atlassian.net/browse/ERM-2612

    • 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

 

Allocations

 

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

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 / Pending Testrails

Closed: Orchid R2023.1

Stories / Bugs

RTL / Tasks

  • NA

Closed (No ERM Release)

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

  • NA

Other

Component Updates

  • NA

Release Planning

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

Testing

Security

  • NA