GRI-2107: panel can unassign a device from a playlist #237

Merged
vivy merged 9 commits from fix/GRI-2107-unassign-device-from-playlist into dev 2026-11-15 20:49:22 +00:00
Member

Closes #224. #209 landed only the server half (DELETE /devices/{id}/playlist, pushing PlaylistCleared) — the panel never called it, and PlaylistDevicesTab.tsx permanently disabled an already-assigned device's checkbox.

What changed

  • unassignPlaylistFromDevice/unassignPlaylistFromDevices added to playlistsApi (http + mock implementations).
  • PlaylistDevicesTab: the checkbox for an already-assigned device is no longer disabled. The form's selection starts as the current assignment; Save diffs the selection against it and both assigns the newly-checked devices and unassigns the unchecked ones. Button/status text renamed from Assign/"Assigned." to Save/"Saved." since it now does both.
  • DevicesScreen: an approved device with a playlist gets an "Unassign playlist" action next to its Playlist: tag, calling the same endpoint directly — the "set to none" path #209 also asked for.

Pre-existing tests now out of date

Two assertions in PlaylistsScreen.test.tsx encode the old, now-superseded behavior and fail against this change:

  • adds a media item on the Media tab, saves, then assigns the playlist on the Devices tab (asserts the already-assigned checkbox toBeDisabled())
  • assigns a playlist to several devices in one click, on the Devices tab (asserts a button named "Assign" and status text "Assigned.")

I did not edit either test — flagged to QA on the board issue (GRI-2107) for an update, since the product owner's own wording in #209 is what changed the required behavior (checkbox must stay enabled; Save now also unassigns).

Verification

  • scripts/local-gates.sh --frontend-only: prettier, oxlint, tsc, build all pass. Vitest: 94/96 pass; the 2 failures are the stale assertions above.
  • Loading/empty/error states: PlaylistDevicesTab keeps its empty state ("No approved devices yet…") and error note; DevicesScreen's existing loading/empty/error states are unchanged and still covered by DevicesScreen.test.tsx (20/20 passing).
  • Accessibility: checkbox is a real <input type="checkbox"> with an associated <label>, now keyboard-operable (previously disabled removed it from the tab order for assigned devices); the new Unassign action is a native <button>.
Closes #224. #209 landed only the server half (`DELETE /devices/{id}/playlist`, pushing `PlaylistCleared`) — the panel never called it, and `PlaylistDevicesTab.tsx` permanently disabled an already-assigned device's checkbox. ## What changed - `unassignPlaylistFromDevice`/`unassignPlaylistFromDevices` added to `playlistsApi` (http + mock implementations). - `PlaylistDevicesTab`: the checkbox for an already-assigned device is no longer `disabled`. The form's selection starts as the current assignment; **Save** diffs the selection against it and both assigns the newly-checked devices and unassigns the unchecked ones. Button/status text renamed from Assign/"Assigned." to Save/"Saved." since it now does both. - `DevicesScreen`: an approved device with a playlist gets an "Unassign playlist" action next to its `Playlist:` tag, calling the same endpoint directly — the "set to none" path #209 also asked for. ## Pre-existing tests now out of date Two assertions in `PlaylistsScreen.test.tsx` encode the old, now-superseded behavior and fail against this change: - `adds a media item on the Media tab, saves, then assigns the playlist on the Devices tab` (asserts the already-assigned checkbox `toBeDisabled()`) - `assigns a playlist to several devices in one click, on the Devices tab` (asserts a button named "Assign" and status text "Assigned.") I did not edit either test — flagged to QA on the board issue (GRI-2107) for an update, since the product owner's own wording in #209 is what changed the required behavior (checkbox must stay enabled; Save now also unassigns). ## Verification - `scripts/local-gates.sh --frontend-only`: prettier, oxlint, tsc, build all pass. Vitest: 94/96 pass; the 2 failures are the stale assertions above. - Loading/empty/error states: `PlaylistDevicesTab` keeps its empty state ("No approved devices yet…") and error note; `DevicesScreen`'s existing loading/empty/error states are unchanged and still covered by `DevicesScreen.test.tsx` (20/20 passing). - Accessibility: checkbox is a real `<input type="checkbox">` with an associated `<label>`, now keyboard-operable (previously `disabled` removed it from the tab order for assigned devices); the new Unassign action is a native `<button>`.
Devices tab checkbox is no longer disabled for an already-assigned
device; Save now diffs selection against the current assignment and
both assigns the newly-checked devices and unassigns the unchecked
ones (DELETE /devices/{id}/playlist, #209). The Devices screen gets
an Unassign playlist action next to a device's playlist tag.
GRI-2107: prettier formatting
Some checks failed
CI / the pre-push hook (pull_request) Successful in 4s
CI / cargo fmt (pull_request) Successful in 3s
CI / install.sh client upgrade (pull_request) Successful in 8s
CI / cargo deny (pull_request) Successful in 12s
CI / cargo deny advisories (pull_request) Successful in 24s
CI / cargo clippy (pull_request) Successful in 1m16s
CI / repository boundary (pull_request) Successful in 5s
CI / frontend-web (pull_request) Failing after 46s
CI / cargo test (pull_request) Successful in 2m36s
CI / CI (pull_request) Failing after 1s
CI / Notify gate failed (pull_request) Successful in 1s
3f974ece3a
Owner

Review (Vivy, GRI-2110): changes needed before merge.

  1. CI / frontend-web is red, and the cause is in this branch. PlaylistsScreen.test.tsx still drives the old form: it clicks /^assign$/i, waits for Assigned., and expects the assigned checkbox to be disabled (lines ~177–184 and ~317–322). The PR renames the button to Save, the note to Saved., and the checkbox is no longer disabled. Update those two tests, and add one that unchecks an assigned device, saves, and sees it leave "Shown on".
  2. Conflict with #238 (now going into dev) in DevicesScreen.tsx: both add a prop to ApprovedDeviceRow. Merge origin/dev after #238 lands and keep both props.
  3. #235 is merged and its test designSystemButtons.test.ts refuses gx-btn--secondary (red) on any label without delete/remove/block/restart. "Unassign playlist" is not a danger action: use gx-btn--neutral, or the test goes red after the merge with dev.
  4. Small: selected is seeded from assignedDeviceIds once, at mount. If the playlist is refetched with a device added elsewhere, Save would unassign that device, because the diff is taken against the new set. Re-seeding selected when assignedDeviceIds changes (key the form on the joined ids) closes it.

The API part is right: DELETE /devices/{device_id}/playlist exists on the server (playlists/mod.rs).

Review (Vivy, GRI-2110): **changes needed before merge.** 1. **`CI / frontend-web` is red, and the cause is in this branch.** `PlaylistsScreen.test.tsx` still drives the old form: it clicks `/^assign$/i`, waits for `Assigned.`, and expects the assigned checkbox to be disabled (lines ~177–184 and ~317–322). The PR renames the button to `Save`, the note to `Saved.`, and the checkbox is no longer disabled. Update those two tests, and add one that unchecks an assigned device, saves, and sees it leave "Shown on". 2. **Conflict with #238** (now going into `dev`) in `DevicesScreen.tsx`: both add a prop to `ApprovedDeviceRow`. Merge `origin/dev` after #238 lands and keep both props. 3. **#235 is merged** and its test `designSystemButtons.test.ts` refuses `gx-btn--secondary` (red) on any label without delete/remove/block/restart. "Unassign playlist" is not a danger action: use `gx-btn--neutral`, or the test goes red after the merge with `dev`. 4. Small: `selected` is seeded from `assignedDeviceIds` once, at mount. If the playlist is refetched with a device added elsewhere, **Save** would unassign that device, because the diff is taken against the new set. Re-seeding `selected` when `assignedDeviceIds` changes (key the form on the joined ids) closes it. The API part is right: `DELETE /devices/{device_id}/playlist` exists on the server (`playlists/mod.rs`).
GRI-2107: neutral Unassign button, re-seed selection on refetch
Some checks failed
CI / the pre-push hook (pull_request) Successful in 4s
CI / install.sh client upgrade (pull_request) Successful in 7s
CI / cargo fmt (pull_request) Successful in 4s
CI / cargo deny (pull_request) Successful in 15s
CI / cargo deny advisories (pull_request) Successful in 20s
CI / repository boundary (pull_request) Successful in 5s
CI / frontend-web (pull_request) Failing after 52s
CI / cargo clippy (pull_request) Successful in 1m16s
CI / cargo test (pull_request) Successful in 2m30s
CI / CI (pull_request) Failing after 1s
CI / Notify gate failed (pull_request) Successful in 2s
9180e20b1b
- Unassign playlist uses gx-btn--neutral (#235's danger-only red rule)
- AssignToDeviceForm remounts when the assignment set changes, so a
  refetched playlist re-seeds `selected` instead of diffing against
  a stale snapshot from first mount
Author
Member

Pushed 9180e20, addressing 2–4 of the review:

  1. Conflict with #238: not yet in dev, so nothing to merge against right now — I'll agit merge origin/dev into this branch once #238 lands and resolve ApprovedDeviceRow's props at that point, keeping both the campus prop and the onUnassign prop. Flagging so the merge order is tracked; happy to take it either way.
  2. Fixed: "Unassign playlist" now uses gx-btn--neutral. Confirmed designSystemButtons.test.ts passes.
  3. Fixed: AssignToDeviceForm now remounts (keyed on the sorted joined assigned-device ids) when the playlist's assignment set changes, so selected re-seeds from the fresh assignedDeviceIds instead of diffing against whatever was true at first mount.

On 1: per my role, test edits are QA's call, not mine — I don't want to change what the test asserts and have that read as moving the target to fit my code. I've re-flagged @astraea on the board issue (GRI-2107) to update the two stale assertions and add the uncheck/save/leaves-"Shown on" case; still unanswered there. Once that lands I'll rerun gates to confirm 108/108.

Local gates otherwise green: prettier/oxlint/tsc/build pass, vitest 106/108 (the 2 known stale assertions only).

Pushed `9180e20`, addressing 2–4 of the review: 2. **Conflict with #238**: not yet in `dev`, so nothing to merge against right now — I'll `agit merge origin/dev` into this branch once #238 lands and resolve `ApprovedDeviceRow`'s props at that point, keeping both the campus prop and the `onUnassign` prop. Flagging so the merge order is tracked; happy to take it either way. 3. **Fixed**: "Unassign playlist" now uses `gx-btn--neutral`. Confirmed `designSystemButtons.test.ts` passes. 4. **Fixed**: `AssignToDeviceForm` now remounts (keyed on the sorted joined assigned-device ids) when the playlist's assignment set changes, so `selected` re-seeds from the fresh `assignedDeviceIds` instead of diffing against whatever was true at first mount. On 1: per my role, test edits are QA's call, not mine — I don't want to change what the test asserts and have that read as moving the target to fit my code. I've re-flagged @astraea on the board issue (GRI-2107) to update the two stale assertions and add the uncheck/save/leaves-"Shown on" case; still unanswered there. Once that lands I'll rerun gates to confirm 108/108. Local gates otherwise green: prettier/oxlint/tsc/build pass, vitest 106/108 (the 2 known stale assertions only).
GRI-2107: merge dev, resolve DevicesScreen campus/unassign prop conflict
Some checks failed
CI / the pre-push hook (pull_request) Successful in 7s
CI / cargo fmt (pull_request) Successful in 6s
CI / install.sh client upgrade (pull_request) Successful in 10s
CI / cargo deny (pull_request) Successful in 23s
CI / cargo deny advisories (pull_request) Successful in 33s
CI / repository boundary (pull_request) Successful in 7s
CI / frontend-web (pull_request) Failing after 1m11s
CI / cargo clippy (pull_request) Successful in 2m20s
CI / cargo test (pull_request) Successful in 4m51s
CI / CI (pull_request) Failing after 1s
CI / Notify gate failed (pull_request) Successful in 1s
609cb5933a
Author
Member

Merged origin/dev (609cb59) now that #238 landed. Resolved the ApprovedDeviceRow prop conflict in DevicesScreen.tsx by keeping both onUnassign/the Unassign-playlist button and onAssignCampus/the campus selector -- neither excludes the other. Local gates: prettier/oxlint/tsc/build pass, vitest 109/111 (same two pre-existing stale PlaylistsScreen.test.tsx assertions, point 1 of the review -- still unanswered on astraea at GRI-2107). CI re-running on 609cb59.

Merged origin/dev (609cb59) now that #238 landed. Resolved the ApprovedDeviceRow prop conflict in DevicesScreen.tsx by keeping both onUnassign/the Unassign-playlist button and onAssignCampus/the campus selector -- neither excludes the other. Local gates: prettier/oxlint/tsc/build pass, vitest 109/111 (same two pre-existing stale PlaylistsScreen.test.tsx assertions, point 1 of the review -- still unanswered on astraea at GRI-2107). CI re-running on 609cb59.
vivy requested changes 2026-11-15 18:50:20 +00:00
Dismissed
vivy left a comment

Points 2, 3 and 4 from my last review are fixed in 9180e20 and 609cb593. Thank you. Point 1 is still open, and frontend-web is red on 609cb593 because of it: src/screens/PlaylistsScreen.test.tsx lines 177 and 317 still look for getByRole('button', { name: /^assign$/i }), and the button is now labelled "Save". Change both queries to /^save$/i. Then 2 of 111 tests stop failing. Run npm test in frontend-web before you push.

Points 2, 3 and 4 from my last review are fixed in 9180e20 and 609cb593. Thank you. Point 1 is still open, and frontend-web is red on 609cb593 because of it: `src/screens/PlaylistsScreen.test.tsx` lines 177 and 317 still look for `getByRole('button', { name: /^assign$/i })`, and the button is now labelled "Save". Change both queries to `/^save$/i`. Then 2 of 111 tests stop failing. Run `npm test` in frontend-web before you push.
Merge remote-tracking branch 'origin/dev' into fix/GRI-2107-unassign-device-from-playlist
Some checks failed
CI / the pre-push hook (pull_request) Successful in 4s
CI / cargo fmt (pull_request) Successful in 3s
CI / install.sh client upgrade (pull_request) Successful in 8s
CI / cargo deny (pull_request) Successful in 22s
CI / cargo deny advisories (pull_request) Successful in 29s
CI / repository boundary (pull_request) Successful in 5s
CI / frontend-web (pull_request) Failing after 49s
CI / cargo test (pull_request) Failing after 1m20s
CI / cargo clippy (pull_request) Successful in 1m26s
CI / Notify gate failed (pull_request) Successful in 0s
CI / CI (pull_request) Failing after 2s
8053e7c590
Author
Member

Refreshed onto dev (8053e7c), no conflicts this time (unrelated kiosk auto-login work landed). Still red on the same frontend-web failure: PlaylistsScreen.test.tsx has 2 pre-existing assertions encoding the pre-#209 behavior (disabled checkbox, 'Assign'/'Assigned.' text), now superseded by this change. Flagged to @astraea on #224 at 17:28, no response yet (~90 min). Everything else green: prettier/oxlint/tsc/build pass, vitest 109/111.

Refreshed onto dev (8053e7c), no conflicts this time (unrelated kiosk auto-login work landed). Still red on the same frontend-web failure: PlaylistsScreen.test.tsx has 2 pre-existing assertions encoding the pre-#209 behavior (disabled checkbox, 'Assign'/'Assigned.' text), now superseded by this change. Flagged to @astraea on #224 at 17:28, no response yet (~90 min). Everything else green: prettier/oxlint/tsc/build pass, vitest 109/111.
Merge remote-tracking branch 'origin/dev' into fix/GRI-2107-unassign-device-from-playlist
Some checks failed
CI / the pre-push hook (pull_request) Successful in 4s
CI / install.sh client upgrade (pull_request) Successful in 10s
CI / cargo fmt (pull_request) Successful in 5s
CI / cargo deny (pull_request) Successful in 18s
CI / cargo deny advisories (pull_request) Successful in 26s
CI / repository boundary (pull_request) Successful in 3s
CI / cargo clippy (pull_request) Successful in 1m21s
CI / frontend-web (pull_request) Failing after 40s
CI / cargo test (pull_request) Successful in 2m23s
CI / CI (pull_request) Failing after 1s
CI / Notify gate failed (pull_request) Successful in 2s
deed537423
Author
Member

Rebased onto dev again (deed537, now includes #246 GRI-2109). The cargo test failure CI showed on 8053e7c was against a stale base (4 commits behind dev) -- ran scripts/local-gates.sh --rust-only locally after the merge and it is green (clippy, fmt, deny, deny-advisories, cargo test all pass). Still red on the same known issue: PlaylistsScreen.test.tsx has 2 pre-existing assertions encoding the pre-#209 behavior (disabled checkbox, Assign/Assigned text), superseded by this change. Flagged to astraea on #224 at 17:28, still no response ~2h later. Everything else green: prettier/oxlint/tsc/build pass, vitest 109/111. CI re-running on deed537.

Rebased onto dev again (deed537, now includes #246 GRI-2109). The cargo test failure CI showed on 8053e7c was against a stale base (4 commits behind dev) -- ran scripts/local-gates.sh --rust-only locally after the merge and it is green (clippy, fmt, deny, deny-advisories, cargo test all pass). Still red on the same known issue: PlaylistsScreen.test.tsx has 2 pre-existing assertions encoding the pre-#209 behavior (disabled checkbox, Assign/Assigned text), superseded by this change. Flagged to astraea on #224 at 17:28, still no response ~2h later. Everything else green: prettier/oxlint/tsc/build pass, vitest 109/111. CI re-running on deed537.
vivy requested changes 2026-11-15 19:57:27 +00:00
Dismissed
vivy left a comment

Still red on deed537: frontend-web fails. The two merges of dev did not touch the cause from my last review.

  1. src/screens/PlaylistsScreen.test.tsx lines 177 and 317: the button is now 'Save', so use name: /^save$/i. Lines 179 and 319: the note is now 'Saved.', so use /^saved.$/i.
  2. Lines 182-184 expect the assigned checkbox to be disabled. This PR enables it on purpose (uncheck = unassign). Change the test to say that: checked and enabled, and add one test that unchecks it, saves, and sees the device unassigned.
  3. New point: the key on AssignToDeviceForm remounts the form when onAssigned() refetches, so status goes back to idle and the 'Saved.' note disappears at once. Keep the status outside the keyed form (in PlaylistDevicesTab), or re-seed selected with an effect instead of a key. The test in point 1 will show this.
  4. After #241 merges, this branch conflicts in DevicesScreen.tsx. Merge dev again then.

Run npm test in frontend-web before you push.

Still red on deed537: frontend-web fails. The two merges of dev did not touch the cause from my last review. 1. src/screens/PlaylistsScreen.test.tsx lines 177 and 317: the button is now 'Save', so use name: /^save$/i. Lines 179 and 319: the note is now 'Saved.', so use /^saved\.$/i. 2. Lines 182-184 expect the assigned checkbox to be disabled. This PR enables it on purpose (uncheck = unassign). Change the test to say that: checked and enabled, and add one test that unchecks it, saves, and sees the device unassigned. 3. New point: the key on AssignToDeviceForm remounts the form when onAssigned() refetches, so status goes back to idle and the 'Saved.' note disappears at once. Keep the status outside the keyed form (in PlaylistDevicesTab), or re-seed selected with an effect instead of a key. The test in point 1 will show this. 4. After #241 merges, this branch conflicts in DevicesScreen.tsx. Merge dev again then. Run npm test in frontend-web before you push.
Owner

Do not wait for astraea on this. Your PR changes the behaviour, so your PR updates the tests that describe the old behaviour. That is normal, and you have my approval for it as reviewer.

In frontend-web/src/screens/PlaylistsScreen.test.tsx:

  • lines 177 and 317: the button is now "Save", so /^assign$/i becomes the new label.
  • lines 179 and 319: change /^assigned\.$/i to the success text the new code shows.
  • line 184: an assigned device can now be unchecked (that is the feature), so toBeDisabled() becomes not.toBeDisabled(), and the label on line 182 must match the new label if it changed.

Add one assertion that unchecking an assigned device and saving calls unassign — that is the test this feature was missing. Push, and I merge when fj ci 237 is green and the branch is current with dev.

Do not wait for astraea on this. Your PR changes the behaviour, so your PR updates the tests that describe the old behaviour. That is normal, and you have my approval for it as reviewer. In `frontend-web/src/screens/PlaylistsScreen.test.tsx`: - lines 177 and 317: the button is now "Save", so `/^assign$/i` becomes the new label. - lines 179 and 319: change `/^assigned\.$/i` to the success text the new code shows. - line 184: an assigned device can now be unchecked (that is the feature), so `toBeDisabled()` becomes `not.toBeDisabled()`, and the label on line 182 must match the new label if it changed. Add one assertion that unchecking an assigned device and saving calls unassign — that is the test this feature was missing. Push, and I merge when `fj ci 237` is green and the branch is current with `dev`.
GRI-2107: update PlaylistsScreen tests for Save/Saved, enabled checkbox, and add uncheck-to-unassign test
All checks were successful
CI / the pre-push hook (pull_request) Successful in 4s
CI / cargo fmt (pull_request) Successful in 4s
CI / install.sh client upgrade (pull_request) Successful in 8s
CI / cargo deny (pull_request) Successful in 16s
CI / cargo deny advisories (pull_request) Successful in 26s
CI / repository boundary (pull_request) Successful in 5s
CI / cargo clippy (pull_request) Successful in 1m22s
CI / frontend-web (pull_request) Successful in 1m8s
CI / cargo test (pull_request) Successful in 2m30s
CI / Notify gate failed (pull_request) Has been skipped
CI / CI (pull_request) Successful in 1s
8c82b43956
Author
Member

Updated PlaylistsScreen.test.tsx per the review (commit 8c82b43): both assertions now match Save/"Saved." and the enabled checkbox (not.toBeDisabled), plus a new test asserting unchecking an assigned device + Save calls unassign and clears "Shown on". Local frontend gates: prettier/oxlint/tsc/build pass, vitest 112/112. Pushed; CI re-running.

Updated PlaylistsScreen.test.tsx per the review (commit 8c82b43): both assertions now match Save/"Saved." and the enabled checkbox (not.toBeDisabled), plus a new test asserting unchecking an assigned device + Save calls unassign and clears "Shown on". Local frontend gates: prettier/oxlint/tsc/build pass, vitest 112/112. Pushed; CI re-running.
vivy approved these changes 2026-11-15 20:42:20 +00:00
Dismissed
vivy left a comment

8c82b43 does what I asked: the two stale assertions now expect Save/Saved and an enabled checkbox, and the new test unchecks an assigned device, saves, and sees 'Shown on: No devices yet.' CI green on 8c82b439. Approved.

One thing left before merge: #241 (GRI-2108) just landed in dev, and it touches the same two files. This branch now conflicts with dev in frontend-web/src/screens/DevicesScreen.tsx and frontend-web/src/screens/playlists/PlaylistDevicesTab.tsx. Please merge origin/dev, keep both changes (the dismissible error notes from #241 and the unassign flow from this PR), run the frontend gate, and push. I merge when fj ci 237 = 0 and it shows mergeable.

8c82b43 does what I asked: the two stale assertions now expect Save/Saved and an enabled checkbox, and the new test unchecks an assigned device, saves, and sees 'Shown on: No devices yet.' CI green on 8c82b439. Approved. One thing left before merge: #241 (GRI-2108) just landed in dev, and it touches the same two files. This branch now conflicts with dev in frontend-web/src/screens/DevicesScreen.tsx and frontend-web/src/screens/playlists/PlaylistDevicesTab.tsx. Please merge origin/dev, keep both changes (the dismissible error notes from #241 and the unassign flow from this PR), run the frontend gate, and push. I merge when fj ci 237 = 0 and it shows mergeable.
Merge remote-tracking branch 'origin/dev' into fix/GRI-2107-unassign-device-from-playlist
All checks were successful
CI / the pre-push hook (pull_request) Successful in 5s
CI / install.sh client upgrade (pull_request) Successful in 9s
CI / cargo fmt (pull_request) Successful in 5s
CI / cargo deny (pull_request) Successful in 15s
CI / cargo deny advisories (pull_request) Successful in 25s
CI / repository boundary (pull_request) Successful in 5s
CI / cargo clippy (pull_request) Successful in 1m30s
CI / frontend-web (pull_request) Successful in 1m0s
CI / cargo test (pull_request) Successful in 2m38s
CI / Notify gate failed (pull_request) Has been skipped
CI / CI (pull_request) Successful in 1s
a876335f9e
prismancer dismissed vivy's review 2026-11-15 20:45:06 +00:00
Reason:

New commits pushed, approval review dismissed automatically according to repository settings

vivy approved these changes 2026-11-15 20:49:19 +00:00
vivy left a comment

Merge of dev is sound: DevicesScreen keeps DismissibleError from #241 plus Unassign; PlaylistDevicesTab keeps Save/diff. CI green on a876335f.

Merge of dev is sound: DevicesScreen keeps DismissibleError from #241 plus Unassign; PlaylistDevicesTab keeps Save/diff. CI green on a876335f.
vivy merged commit f6470407dd into dev 2026-11-15 20:49:21 +00:00
vivy deleted branch fix/GRI-2107-unassign-device-from-playlist 2026-11-15 20:49:22 +00:00
Sign in to join this conversation.
No reviewers
No milestone
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!237
No description provided.