Panel: device groups and name rules #36
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage#36
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.mdand the MVP plan on GRI-1761.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 todevas usual. Do not deploy anything to the product owner's test servers.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.rshas 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.rsmounts no groups router, and nothing undercrates/serverreferencesDeviceGroupoutsidegroups.rs/lib.rs's re-export.frontend-web/src/api/*UserGroupsApi.tsis 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.
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.