Page History

• Attendees / Apologies
• Upcoming Availability

NA

Release Candidates

Code Review: 

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

   /

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

  /

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

  • 1608: test procedure works locally, previous change request not replicated

QA / UAT 

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

  • Can't be tested because licenses not working on folio-snapshot
  • grails upgrade reverted from 4.0.10 back to 4.0.4 which should resolve
  • Owen to ask for rebuild

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

  /

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

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

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

Items at Risk / Spillover

In Progress

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

• 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-1542

  • setPrimaryOrg on change not worked
    • workaround with separate component does work
    • draft PR to be raised for Ethan to review
  • default role value addressed by checking / treating first render row differently
    • renderRoles function in renderRoles array
    • critical for validation
  • validation checks
    • role 
      • stated preferred approach would be significantly more costly (development time and code performance)
      • expedient: validator that uses all values, checking role array, non-destructively
    • organisation:
      • need to 'validate' through the field that identifies the card for organization, something like orgs.UUID 
      • though technically not a form validation. should handle as per self-linking agreements (useEffect)
      • not sure how to refer to values to compare: can be had from useFormState. 

• 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-1543

  • done, pending related issues

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

  • couldn't progress because of licenses issues on snapshot
  • can call ui-plugin-find-agreement from either
    • erm-comparisons search and sort
    • dashboard: simple search widget filter
    • agreements: related agreements 

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

  • can swap parameter this.actionName as null
  • and ifPermission with hasPerm
  • rather: take extensible pattern from viewAgreement.js

Sprint Backlog

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

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

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

Needs Elaboration

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

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

Bugfix Cycle

• NA

mod-serv-int has been added to folio-testing vagrant image

• this needs to be removed
• Ethan and Ian investigating

New Issues

Added to sprint

• NA