/
2022-05-11 ERM Weekly Delivery Update

2022-05-11 ERM Weekly Delivery Update

May 11, 2022

Meeting Details

Date

May 11, 2022 

Time

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

Location

Video Call in

Previously

2022-04-27 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya 

  • @Monireh Rasouli 

  • @Ethan Freestone 

  • @Claudia Malzer 

  • @Gill Osguthorpe 

Apologies

  • Peter Bohm

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

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

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

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

    • Progress / Impediments: 

      • trying to follow existing BigTest but getting strange error

    • TODO: 

      • check that each checkbox is rendered

      • check that checking them toggles their status (or all, if the select all)

    • New unknowns: do not need to mock the button

    • Help or input needed: NA

    • ETA for review:  

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

    • Progress / Impediments: 

    • TODO: 

      • Develop according to the design note (web-toolkit-ce)

        • implement multiValueRefData class

        • write backend tests for multi and single value properties

        • confirm shape for okapi interface to handle multivalue shape 

        • then (front end)

          • add mv options to refdata component

          • add setting data to edit component

      • Frontend design (stripes-kint-components)

        • multi-value picklist types (setting values) 

          • for consistency, existing pattern exists for multi-select (as used in organisations)

        • settings entry: no new design work yet, but options will be needed to be added

        • filter builder: no change expected for now

    • New unknowns: 

      • how do we treat new permissions (eg treat as mutable values)

      • filter builder may n

    • Help or input needed: 

    • ETA for review: 

 

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

 

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

NA

  • ISSUE

    • Blocking conditions

    • Action needed

Needs Elaboration

NA

Sprint Backlog - Next Up

  • Claudia:  RTL

  • Ethan:  ERM-2123 development

  • Monireh: RTL

  • Peter:  ?

 

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 

 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

Accepted

Carried Forward

Closed: Kiwi Hot Fix #3

Closed: Lotus Hot Fix #1

Closed: Morning Glory R2022.2

Features

RTL / Other Tests

  • NA

Other / babel-eslint

Closed (No ERM Release)

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

Other

Translations: what don't we understand?