2020-12-09 ERM Weekly Delivery Update

2020-12-09 ERM Weekly Delivery Update

Meeting Details

Date

Dec 9, 2020    

Time

10:30am ET, 3:30pm UK, 4:30pm Germany

Location

Video Call in FOLIO Slack: #erm-developers

Previously

2020-12-02 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Gill Osguthorpe

  • @Ethan Freestone

  • @Aditya matukumalli

  • @Peter Böhm

  • @Claudia Malzer

  • @Owen Stephens

Apologies

Discussion items

Time

Item

Notes

Action Items

Time

Item

Notes

Action Items

<5 mins

Introductions





WIP Update 

Release Candidates

Code Review: 

QA / UAT 

Items at Risk / Spillover

In Progress

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

    • Previously TODO (A few days effort still expected because of configMgr complexity):

      • use translation strings

      • using values in MCL

      • tests

    • Still having issues

    • Agreement Line takes to AL view pane. 

      • what should happen if view is closed? 

      • no other FOLIO apps have load more option within MCLs

      • preference is to maintain current load state if switching out and returning to the list

      • Turns out this is an existing bug: out of scope for this story. Owen to write up bug issue. 

    • Owen to clarify story: 

      • variabilise row count per page (currently 100 to user defined)

      • add user setting to allow this to be set.

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

    • changed width to 25% and looks good

    • to add more browser options

    • will then be ready for code review on Thursday

    • Adi to send Peter link to Jenkins to follow PR build process

Sprint Backlog

Needs Elaboration

  • NA

Closed

No documentation required or development feedback to give.



<10 mins

AOB

New Issues

Added to sprint

Not added to sprint

  • NA

Sprint 104-105 Planning

  • License date search expected - will require some toolkit changes

  • Move to 2pm-3pm (UK) on Monday

Keyboard Shortcuts Requirements

  • Feedback provided to KG and JC

  • Proposal is doable, but will likely need some changes to existing components

  • Need more input from JC and GO to estimate