Child pages
  • 2020-12-09 ERM Weekly Delivery Update

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Meeting Details

Date

    

Time

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

LocationVideo Call in FOLIO Slack: #erm-developers
Previously2020-12-02 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

...

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions



WIP Update 

Release Candidates

Code Review: 

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1228
    • ready for review
    • Ethan Freestone to attach wireframe to issue for reviewing against

QA / UAT 

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1176
    • waiting for folio-testing to update

Items at Risk / Spillover

In Progress

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-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.
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-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

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1249
    • waiting for update
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1242

Needs Elaboration

  • NA

Closed

No documentation required or development feedback to give.

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1204
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1243
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1229
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1137
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1148
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1225


<10 minsAOB

New Issues

Added to sprint

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1252
    • to be picked up by Peter

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