• Attendees / Apologies
• Upcoming Availability

NA

Code Review: 

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

  • integration tests reviewed:
    • does not gel with existing tests
    • will need new values and possible tests
  • refactor on tests should not block QA 
  • some testing has been done to check against the ingest process
  • transferred to Owen for QA
  • new subtask raised to track integration test tweaks:

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

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

  • some scenarios missing and not identified
  • to follow up with Adi post-call

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

  /

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

QA / UAT 

• No issues expected

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

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

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

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

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

  • need to review for potential testing issues
  • empty accordians aren't shown anymore so circumstances for issue arising are rarely triggered

Bugfix Cycle 

• NA

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

  • locally,
    • internal contacts are not linked
    • need to select agreement twice to enable linkable admin contact
    • users are not added in local build of platform-erm
  • not the same on snapshot -
    • shouldn't need to worry about it
    • may be separate bug: 
      • Owen to review 
      • would be a good place to use react query
      • if so, then should come up with a pattern first

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

  • just started
  • agreements.js, eresources and platforms will take a significant time - completely
    • use sas from smart-components
    • potentially 4 days
  • other tests should be 4-5 days

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

  • not seeing the reason tests are 

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

  • Adding 'relatedTitles' to the expansion list doesn't make any difference.
  • Some formatting to the issue description to highlight the differences between the scenarios.
  • To try alternative approach: 
    • ti not pti
    • ti.work.titles that aren't current
    • titles shouldn't be fully rendered

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

  /

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

  • front-end issue (stripes-erm-components)
  • two approaches considered
  • choice is when custom properties are created, ignore everything unless value is entered
    • rather than validate dirty fields
  • will add a delete prop as default for primary properties

Sprint Backlog - Next Up

• Claudia:
  • potentially

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

  • recent example in ERM-1859
  • may need to add similar more in other issues
    • Gill to review and liaise with Owen to raise relevant issues
• Peter: 

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

• Ethan: 
  • Release Tasks

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

    Integration tests for ERM-1798
  • ERM-1799
• Adi: 
  • RTL tasks not requiring SaS/smart-components
  • Frontend Release Tasks
  • RTL tasks using SaS/smart-components
• Monireh: RTL tests

Sprint Backlog - to follow

• NA

Needs Elaboration

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

Blocked

• NA

Sprint Backlog 

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

  • at risk this sprint because of extra time needed for new sas related RTL tests for ERM-1661 

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

Accepted 

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

  • should be good to close 
  • no testrail cases to be raised

New Issues

Added to sprint

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

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

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