\uD83D\uDCAD Checklist
Testing
- Identify tickets that require UI load testing for long lists/tables.
- Identify tickets that require Karate tests.
- Review Karate Jenkins job results
- Identify tickets that require performance testing.
Delivery
- Review completed tickets and decide if release notes should be updated:
- Required migrations
- Config changes
- New/changed permissions
- Breaking schema changes
- Re-indexing changes
- Known issues
- MARC mappings changes
- 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
- Pavlo Smahin to 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 to update Q release notes related to create/update permissions
- Christine Schultz-Richert to review Call-number Confluence page with requirements