• Release Candidates

  • Code Review - NA

  • QA / UAT 

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

       

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

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

      • blocked by ERM-633

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

• Items at Risk / Spillover
  • Open / Sprint Backlog

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

      • Effectively a workaround, closed to be superceded by ERM-592

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

      • closed - cannot fully reproduce. 
      • some clipping still manifest: to be progressed thru STCOM-631 (expecting to be picked up by John Coburn)

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

      • promoted to separate issue to unblock ERM-625
      • Assigned to Claudia
      • Hope to resolve on Friday
    • With Steve 

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

         - to carry over

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

         
        • potentially fixed - Ian to confirm with Steve.
        • aim to complete in order to unblock ERM-584
  • In Progress

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

      • should all be ready to QA, except elements relating to ERM-575

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

       
      • expect ready for QA Fri

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

       

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

      • expect ready for QA Fri

Brought into sprint: 

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

   / 

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

   - Mark to pick up

New and to be reviewed for progress: 

• NA

• TBC

• UX issues that are cross-app need addressing outside of ERM
• Added ux-todo  label to distinguish from ERM issues
• Migrated to UXPROD project for resolution
  • ERM-499 >

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

  • ERM-598 > 

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

•  Ian Ibbotson to raise with AppInt the question of who can action these.