E2-F5: Away Match Stadium Creation¶
Epic: E2: Match & Stadium Management
Size: S (Small)
Problem / Outcome¶
Admins create stadium configurations for away matches (external venues).
Scope¶
In-Scope:
- Create away stadium (name, city, country)
- Define sectors with capacity
- Non-numbered ticket option
- Technical seats allocation
Out-of-Scope:
- Seat map import (separate feature)
Acceptance Criteria¶
- AC1: Given away match, when admin creates stadium, then stadium saved with match association
- AC2: Given stadium, when admin marks as "non-numbered", then tickets sold without seat assignment
- AC3: Given away stadium, admin can define sectors with total capacity and technical seats
Data Model Impact¶
Stadium table:
- type (ENUM: HOME, AWAY)
- is_numbered (BOOLEAN)
- country (VARCHAR) - for away stadiums
AwayStadiumSector table:
- id (UUID, PK)
- stadium_id (UUID, FK)
- name (VARCHAR)
- total_capacity (INTEGER)
- technical_seats (INTEGER)
Permissions/Roles¶
- Admin (Match Manager)
How to Verify¶
npm test -- --grep "away stadium"
Expected: Away stadium creation works, non-numbered flag persists.
Dependencies¶
Implementation Tasks¶
See E2: Match ## Doc References Stadium Tasks
Doc References¶
Last Updated: January 2026