Prevent direct 'running' status transitions in kanban
Cluster 19535. Data as of
Nothing open on GitHub. Fix merged in #19916 on 4 May 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #19916. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #19705. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address enforcing kanban workflow rules by rejecting or preventing direct status writes that bypass the expected transition path into 'running'. One item also includes a UI contrast improvement alongside the transition control.
Open issues0
Open PRs0
Fixes on record
-
#19705 fix(kanban): reject direct status transition to 'running' via dashboard API (salvage of #19554)
files:
plugins/kanban/dashboard/plugin_api.py,tests/plugins/test_kanban_dashboard_plugin.py -
#19916 feat(kanban-dashboard): sharper home-channel toggle contrast, drop → running action
files:
plugins/kanban/dashboard/dist/index.js,plugins/kanban/dashboard/dist/style.css
1 PR closed without merging
From the close comments: duplicate 1
-
#19554 fix(kanban): reject direct status transition to 'running' via dashboard API · duplicate →
#19535
Closed issues · 1
- Closed#19535fix(kanban dashboard): prevent direct status writes into running
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab