Goal:
Allow assigning a single team to each event, similar to how tags work — but with a stricter structure and controlled creation.
Behavior
- Each event can be linked to exactly one team (or none)
- Teams are not created on-the-fly like tags — they must be created explicitly via a dedicated interface or API
- Teams have:
id (UUID)
name (required, unique)
description (optional)
Backend Tasks
Frontend Tasks
Notes
- Only one team can be assigned to an event
- Team assignment is meant for organizing ownership/responsibility — not for filtering or tagging like tags
Goal:
Allow assigning a single team to each event, similar to how tags work — but with a stricter structure and controlled creation.
Behavior
id(UUID)name(required, unique)description(optional)Backend Tasks
Teammodel:id(UUID)name(str, unique, required)description(str, optional)team_idto theEventmodel (nullable FK)GET /events,GET /events/{id})team_idin event creation and update endpointsPOST /eventsPATCH /events/{id}GET /teamsPOST /teamsDELETE /teams/{id}Frontend Tasks
GET /teamsNotes