/
2022-09-21 ERM Weekly Delivery Update

2022-09-21 ERM Weekly Delivery Update

Sep 21, 2022

Meeting Details

Date

Sep 21, 2022 

Time

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

Location

Video Call in

  • FOLIO Slack: #erm-developers

  • Backup (Meet): https://meet.google.com/oei-okoc-eys

Previously

2022-09-14 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya 

  • @Ethan Freestone 

  • @Owen Stephens 

  • @Monireh Rasouli 

  • @Gill Osguthorpe 

  • @Claudia Malzer 

Apologies

  • Peter Boehm

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

To pick up in mid-sprint review on Monday

 

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-2279

    • Progress / Impediments: Just started

    • TODO: all

    • New unknowns / help or input needed: NA

    • ETA for review: 

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

    • Progress / Impediments: 

      • PR raised

      • no label, just value for identifiers

      • tests extended

    • TODO: 

      • switch type and identifier column

    • New unknowns / Help or input needed: NA

    • ETA for review: Today

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

    • Progress / Impediments: 

      • Cannot determine why the PO lines return is empty as PO line is always empty if no permission, so "No PO lines message is shown" ... however, should know permission without retrieving PO lines

    • TODO: 

      • root out where PO lines array content is suppressed by ERM backend

      • refactor depending on whether array is empty or not

    • New unknowns / Help or input needed

    • ETA for review: Today

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

    • Progress / Impediments: Done

    • TODO: push for code review

    • New unknowns / help or input needed: NA

    • ETA for review: Today

 

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

Needs Elaboration

Sprint Backlog - Next Up

 

 

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

 

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 

Bugfix Cycle 

  • NA

 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

For Release / Pending Testrails

Closed: Nolana R2022.3

Stories / Bugs

RTL / Tasks

  • NA

Previously

Closed (No ERM Release)

  • NA

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

  • NA

Other

  • SKC is at 3.0, so workspace and local environments should be nuked/updated

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

    • dismissable UI message in Scenario 7 not delivered

    • need to find a good way to determine how many users are affected

    • need a pattern for communicating changes that affect multiple users without adding noise

    • to be handled separately from the rest of ERM-2314, which is ready to release