Groups represent timezone-based screening cohorts, but submission closure and reel publication are currently controlled only for the whole year. Admins should be able to close each group independently, making that group's reel available without exposing groups whose submissions remain open.
Current behavior
Requested behavior and build scope
- Persist and expose submission-closure state for each group, with admin controls alongside the existing year administration.
- Apply the project's group closure to project, media, and video write permissions; preserve archived-year locking.
- Publish only closed groups to non-admin playlist requests, with filtering enforced server-side; admins retain preview access.
- Reflect per-group availability in project and watch-page navigation.
- Define the closure behavior for ungrouped projects as part of this work.
- Cover mixed open/closed groups in repository, API authorization, and UI tests.
Requested by daniel.
--
View Junior Session [Sentry]
Groups represent timezone-based screening cohorts, but submission closure and reel publication are currently controlled only for the whole year. Admins should be able to close each group independently, making that group's reel available without exposing groups whose submissions remain open.
Current behavior
years.submissions_closedis the only persisted closure state.listPlaylistauthorizes the entire year, returns every ready group, and the watch page filters groups only in the browser.Requested behavior and build scope
Requested by daniel.
--
View Junior Session [Sentry]