Items at Risk / Spillover

• Open / Sprint Backlog

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

    • should be ready to test Friday

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

    • should be ready to test Thursday

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

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

• In Progress

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

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

    • Resolved as part of ERM-508

Release Candidates

• Code Review:

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

    • backend completed
    • some front-end issues to fix
    • expected to be ready to QA Thursday

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

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

• QA / UAT: 

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

    • Uncovered new bug (to be raised), that only the first harvesting from GOKb works - subsequent harvests do not execute.
    • RBSync status is not changed from In Progress. 
    • Import outcome logged as failure rather than partial. 
    • this issue will be ready to progress

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

    • merged today - ready to QA Thu

• will hit the same kind of performance issues that were faced with package content
• code is in place to handle this as described, but seems to have regressed
• bringing into active sprint