Skip to content

E2-F6: Match Update Notifications

Epic: E2: Match & Stadium Management

Size: S (Small)

Problem / Outcome

When match details change, ticket holders should be optionally notified.

Scope

In-Scope:

  • Notification preference on match update (notify all / silent update)
  • Email notification to ticket holders
  • Push notification to ticket holders
  • Audit logging for all changes

Out-of-Scope:

  • Rescheduling with ticket revalidation (covered in cancellation)

Acceptance Criteria

  • AC1: Given match update with "Notify", when saved, then push and email sent to all ticket holders
  • AC2: Given match update with "Silent", when saved, then no notifications sent, audit log records silent update
  • AC3: All changes logged in audit trail regardless of notification setting

Data Model Impact

MatchAuditLog table:
- id (UUID, PK)
- match_id (UUID, FK)
- changed_by (UUID, FK)
- change_type (ENUM: update, cancel, reschedule)
- notification_sent (BOOLEAN)
- changes_json (JSONB)
- created_at (TIMESTAMP)

Permissions/Roles

  • Admin (Match Manager)

How to Verify

npm test -- --grep "match notification"

Expected: Notification preference honored, audit trail complete.

Dependencies

Implementation Tasks

See E2: Match ## Doc References Stadium Tasks

Doc References

Last Updated: January 2026