E10-F4: Emergency Ticket Printing¶
Epic: E10: Customer Support Operations
Size: S (Small)
Problem / Outcome¶
Print tickets on match day for fans without phone access.
Scope¶
In-Scope:
- Ticket lookup by various criteria
- Identity verification requirement
- Print with "EMERGENCY REPRINT" watermark
- Audit logging
Out-of-Scope:
- Regular ticket printing
Acceptance Criteria¶
- AC1: Given valid ticket and ID match, agent can print ticket
- AC2: Printed ticket includes "EMERGENCY REPRINT" watermark
- AC3: Print event logged with agent ID and reason
Data Model Impact¶
PrintLog table:
- id (UUID, PK)
- ticket_id (UUID, FK)
- agent_id (UUID, FK)
- reason (VARCHAR)
- identity_verified (BOOLEAN)
- verification_document_type (VARCHAR)
- print_location (VARCHAR)
- printed_at (TIMESTAMP)
Printed ticket includes:
- EMERGENCY REPRINT watermark
- Original QR code
- Seat details
- Print timestamp
- Agent reference
Permissions/Roles¶
- Admin (Box Office Staff)
How to Verify¶
npm test -- --grep "emergency print"
Expected: Print generates, audit logged.
Dependencies¶
Implementation Tasks¶
See E10: Customer Support Tasks
Doc References¶
Last Updated: January 2026