/
2022-11-16 ERM Weekly Delivery Update

2022-11-16 ERM Weekly Delivery Update

Nov 16, 2022

Meeting Details

Date

Nov 16, 2022 

Time

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

Location

Video Call in

Previously

2022-11-09 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Monireh Rasouli 

  • @Gill Osguthorpe 

  • @Ethan Freestone 

  • @Claudia Malzer 

  • @Owen Stephens 

Apologies

 

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

https://folio-org.atlassian.net/browse/ERM-2431 - Deployed?

https://folio-org.atlassian.net/browse/ERM-2445

  • Remedial action clear

  • To complete today

 

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

    • Progress / Impediments: unknown - absent dev 

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

    • Progress / Impediments: 

    • TODO: focus on appearance of tables

      • Set up routing from/packages/ to use logic in eResources view

      • Change navigation links from

        • PTI / Agreement Lines

        • (no change needed within plugins)

      • Ensure routing in index is correctly described when in /package|title/id 

      • Remove permissions for responsive button group

      • Add Titles and Packages filters (to replace eResource filters - no need to change the latter)

    • New unknowns: 

      • What should the workflow / ux be when moving from agreement line

    • Help or input needed:

      • Only 1 Route? 

        • Shouldn't need separate Title or Package View

        • Should pass straight to existing eResource Route/View, which contains the logic

      • Separate icons for packages and titles

    • ETA for review: 

 

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

Needs Elaboration

  • NA

Sprint Backlog - Next Up

Others

 

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

Removed

 

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 

Waiting for snapshot to rebuild

Bugfix Cycle 

 

 

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 Bugfix

Stories / Bugs

  • NA

RTL / Tasks

  • NA

Release Tasks

  • NA

Previously

  • NA

Closed: Orchid R2023.1

Stories / Bugs

  • NA

RTL / Tasks

 

Closed (No ERM Release)

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

  • NA

Other

Component Updates

  • NA

Release Planning

  • NA

Testing

Improved FormattedDateTime Interactor Pattern

  • whitespace character &nbsp; causes test failures when checking for date/time

  • new FormattedDateTimeInteractors have been set up

  • does require passing an id to filter by

  • EF will add change to stripes-erm-testing and stripes-erm-components.

  • Will require bump to 1.1.0