Release Candidates

For Release

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

Code Review: 

• NA

QA / UAT 

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

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

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

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

  • Returned to Code Review to incorporate additional change for agreement lines.
  • Waiting for Jenkins build issue to be resolved - long queue of tasks from other repositories to process before PR is reviewable

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

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

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

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

Items at Risk / Spillover

In Progress

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

  • Waiting for Jenkins build issue to be resolved - long queue of tasks from other repositories to process before this can be QAd

Sprint Backlog

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

  • the agreement name is being changed as if by poltergeists, because according to Grails 4 this shouldn't be happening. 
  • Ethan to investigate whether we are using any special logic
  • May need to hand to Steve

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

  • Adi to investigate

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

  • not started yet

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

  • to be picked up by Claudia
  • message banner should be persistent. as per standard component behaviour
  • similar in local-kb-admin

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

  • logging levels are intentionally set
  • Closing issue as Won't Fix as logging levels 
  • Separately
    
    • Owen Stephens to review logging levels as per 

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

  • May be related to logback.groovy file setting for development environments

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

• • a fix (for this and 1079) would be to make all permissions defined at a granular level
  • Not tricky, just time-consuming
  • OS advised to hold off on this for now
  • Reverted to reporter for clarification on why it is needed
  • Removed from sprint.

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

Blocked

• NA

Needs Elaboration

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

  • ERM-1155 Ethan to write up handlebars approach
  • To feed into re-writes and redesigns of ERM-1048, ERM-1107, ERM-1109
    • expect to still show users example URLs

Release Tasks

• Issues ERM-1165 to ERM-1174 added 
• JG to assign.

• may be solved by ERM-972 972 if granular permissions are defined
• not a priority to fix for Honeysucklebring into sprint once that is addressed for QA