• Attendees / Apologies
• Upcoming Availability

NA

Release Candidates

Code Review: 

• NA

QA / UAT 

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

For Release

• NA

Items at Risk / Spillover

In Progress

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

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

  • can replicate, but not found source yet
  • using new user with local permissions
  • buttons.length is returned as 0 rather than 1 when hasPerms = 1
    • try replacing buttons as a variable with a state (to force full re-render)
    • looks like running this before it has checked perms
      • could be an asynchronous race condition issue
      • may work with async function and a .then, though this is increasingly messy
  • menu options are transferred to another component.
    • switching to a function to directly call using {p}=> this.getActionMenu(p)
  • stripes-components has Memo-ised

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

  • some issues with backend / vagrant setup, with timeouts on the vagrant box rather than locally
  • getting sorting issue locally but not on snapshot,
    • correct in response, but wrong on presentation 
  • not tested the 1000 limit, as shared snapshot environment
    • request looks right
    • clear to progress to merge for bugfest
  • TODO: check whether extra sorting is happening

Sprint Backlog

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

  / 

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

  • shoudl be a quick fix - will pick up at next start of day before getting stuck into 1619/1620

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

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

  /

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

  /

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

  / 

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

  • dependent on backend fixing
  • suggested aligning with version Ethan and Owen are using - see https://folio-project.slack.com/archives/CAYCU07SN/p1618407618023700

Needs Elaboration1

• NA

For Release / Closed

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

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

  /

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

   

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

New Issues

Added to sprint

• NA