Release Candidates

Code Review: 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1228

  • ready for review
  • Ethan Freestone to attach wireframe to issue for reviewing against

QA / UAT 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1176

  • waiting for folio-testing to update

Items at Risk / Spillover

In Progress

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key 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.

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key 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

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1249

  • waiting for update

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1242

  • been researching based on other FOLIO dev recommendations. 
  • some resources for RTL/Jest -> UI Unit testing with Jest/Bigtest
  • expect to begin writing tests today

Needs Elaboration

• NA

New Issues

Added to sprint