Panel: device groups and name rules #36

Open
opened 2026-11-07 18:58:08 +00:00 by vivy · 3 comments
Owner

What

Create groups, edit name rules, assign playlists to a group.

Done when

Groups are managed from the panel.

Depends on

#35, #23

Plan

plan/frontend/stack.md


Routing/Hold: no agent is routed to this issue automatically. To take it yourself, assign yourself. Vivy removes the hold when it is handed to an agent.
Created for GRI-1818 from plan/overview/roadmap.md and the MVP plan on GRI-1761.

## What Create groups, edit name rules, assign playlists to a group. ## Done when Groups are managed from the panel. ## Depends on #35, #23 ## Plan plan/frontend/stack.md --- `Routing/Hold`: no agent is routed to this issue automatically. To take it yourself, assign yourself. Vivy removes the hold when it is handed to an agent. Created for GRI-1818 from `plan/overview/roadmap.md` and the MVP plan on GRI-1761.
Author
Owner

Released for work (chief of staff, 2026-11-16, on the product owner's go-ahead to continue with the next phases). Branch from dev, PR to dev as usual. Do not deploy anything to the product owner's test servers.

Released for work (chief of staff, 2026-11-16, on the product owner's go-ahead to continue with the next phases). Branch from `dev`, PR to `dev` as usual. Do not deploy anything to the product owner's test servers.
Member

Picked this up as glamourweaver. Dependencies (#35, #23) are closed, but on inspection the groups panel has no contract to build against yet, so I'm blocking rather than guessing at an API:

  • crates/server/src/groups.rs has the pure domain model (DeviceGroup, NameRule, matches/claims) from #35, but there is no HTTP route, no handler, and no store/persistence for device groups — crates/server/src/http.rs mounts no groups router, and nothing under crates/server references DeviceGroup outside groups.rs/lib.rs's re-export.
  • "Assign playlists to a group" has no backend shape either — no group↔playlist relation exists anywhere in the server crates.
  • No QA-written frontend tests exist for a groups screen. frontend-web/src/api/*UserGroupsApi.ts is the unrelated user-permissions-groups feature, not device groups.

Needed before I can implement: the backend engineer to land the HTTP API (CRUD on groups, name-rule validation surfaced to the client, playlist assignment) and the test writer to land the panel's tests. Flagging to the CTO to route those.

Picked this up as glamourweaver. Dependencies (#35, #23) are closed, but on inspection the groups panel has no contract to build against yet, so I'm blocking rather than guessing at an API: - `crates/server/src/groups.rs` has the pure domain model (`DeviceGroup`, `NameRule`, `matches`/`claims`) from #35, but there is **no HTTP route, no handler, and no store/persistence** for device groups — `crates/server/src/http.rs` mounts no groups router, and nothing under `crates/server` references `DeviceGroup` outside `groups.rs`/`lib.rs`'s re-export. - "Assign playlists to a group" has no backend shape either — no group↔playlist relation exists anywhere in the server crates. - No QA-written frontend tests exist for a groups screen. `frontend-web/src/api/*UserGroupsApi.ts` is the unrelated user-permissions-groups feature, not device groups. Needed before I can implement: the backend engineer to land the HTTP API (CRUD on groups, name-rule validation surfaced to the client, playlist assignment) and the test writer to land the panel's tests. Flagging to the CTO to route those.
Member

Re-verified after today's reassignment: no change. crates/server/src/http.rs still has no groups router/handlers/store, and there is still no device-group-to-playlist relation anywhere in the server crates. frontend-web still has no groups-screen tests. Still blocked on the backend engineer landing the HTTP API and the test writer landing the panel tests (CTO to route) -- see prior comment for the full breakdown.

Re-verified after today's reassignment: no change. crates/server/src/http.rs still has no groups router/handlers/store, and there is still no device-group-to-playlist relation anywhere in the server crates. frontend-web still has no groups-screen tests. Still blocked on the backend engineer landing the HTTP API and the test writer landing the panel tests (CTO to route) -- see prior comment for the full breakdown.
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoire-of-digital-signage#36
No description provided.