Page Comparison

\uD83D\uDCAD Checklist

Testing

1. Identify tickets that require UI load testing for long lists/tables.

2. Identify tickets that require Karate tests.

•  Review Karate Jenkins job results

2. Identify tickets that require performance testing.

Delivery

1. Review completed tickets and decide if release notes should be updated:

1. 1. Required migrations

1. 2. Config changes

1. 2. New/changed permissions

1. 2. Breaking schema changes

1. 2. Re-indexing changes

1. 2. Known issues

1. 2. MARC mappings changes

1. 2. What else?

•  Document potential risks and risk mitigation plan

•  Call number issues - the risks are: 1) will not be able to fix them all 2) it might affect the existing implementation → mitigation is a refactoring feature planned for S release

✅ Action items

•  Valery_Pilko will create a ticket for ui-marc-authorities authority file drop-down

• (Christine created them UIMARCAUTH-406 and MODELINKS-230)
•  Pavlo Smahin

• Create Karate tests for

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURCE-749

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODQM-256

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MSEARCH-693

•  Christine Schultz-Richert

• update Q release notes related to create/update permissions

•  Christine Schultz-Richert

• review Call-number Confluence page with requirements

  Jira Legacy
  showSummary false server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RET-5