charles/claude-hooks

Fork

You've already forked claude-hooks

Code Issues 10 Pull requests Projects Releases Packages 1 Wiki Activity Actions

B1 — Planner board: drop-to-unassign (close the loop) #409

New issue

Closed

opened 2026-04-27 00:01:33 +00:00 by claude-desktop · 0 comments

claude-desktop commented

2026-04-27 00:01:33 +00:00

Collaborator

Copy link

As an operator,
I want to drag a card back into the Unassigned column,
so that I can clear a wrong assignment in one gesture without flipping to the Forgejo UI.

Today the synthetic Unassigned column is read-only — apps/web/src/components/board/board-column.tsx:42 sets isDropTarget = column.type !== "unassigned", and apps/web/src/components/board/board.tsx:79 rejects drops onto it. Operators must either re-drag onto a different agent column or open Forgejo to clear the assignee. This story closes the loop.

Acceptance criteria

Frontend

Reverse the isDropTarget guard in board-column.tsx so the Unassigned column accepts drops.
handleDrop in board.tsx calls the existing assignCard mutation with assignee: null when the target column is the Unassigned synthetic.
Optimistic update moves the card immediately; the existing rollback path (TanStack Query mutation onError) restores the source column on failure.
Drag-from-Unassigned-onto-Unassigned is a no-op — early return before any API call, no visual flicker.
If the card has a running task on the previous agent, show a confirm dialog (AlertDialog) before completing the drop. Dialog copy: Cancel running task on @{previousAgent} and unassign? with Confirm / Keep assignment actions.
On confirm, the assignment mutation calls POST /board/assign { assignee: null, cancel_running: true } (extend body — see backend section).

Backend

POST /board/assign accepts assignee: null and clears the Forgejo assignee via PATCH /repos/:owner/:name/issues/:index with { assignees: [] }.
When body includes cancel_running: true, cancel the in-flight task on the previous agent (mirror /board/reroute's cancellation logic) and post an audit comment on the issue: Unassigned by @{actor} via board (running task cancelled).
When body omits cancel_running but the issue has a running task, return 409 { error: "running_task_present", running_agent: "<login>" } so the frontend can prompt.

Tests

board.test.tsx: drag from dev column to Unassigned → assignCard called with assignee: null + cache patch.
board.test.tsx: same drag with running task → 409 → confirm dialog → second call with cancel_running: true.
board.test.tsx: drag-from-Unassigned-onto-Unassigned → no API call.
Server test for /board/assign: assignee: null clears Forgejo assignee + (when cancel_running) cancels task + posts audit comment.

Out of scope

Drop-to-unassign on issues that are not type:user-story (server filter unchanged).
Multi-card drop-to-unassign — covered by B3 (multi-select stack-drag).
Per-instance unassignment — out of scope until per-instance columns ship.

References

Spec: docs/specs/board-rework.md §5 B1.
Current board route: apps/web/src/routes/planner.board.tsx.
Drag handlers: apps/web/src/components/board/board-column.tsx, board.tsx.
Existing assign API: apps/server/src/domain/views/board.ts (POST /board/assign, POST /board/reroute).
Original board spec: M18-7 / #168.

Suggested first commit

feat(board): drop-to-unassign clears assignee in one gesture

**As an** operator, **I want** to drag a card back into the Unassigned column, **so that** I can clear a wrong assignment in one gesture without flipping to the Forgejo UI. Today the synthetic Unassigned column is read-only — `apps/web/src/components/board/board-column.tsx:42` sets `isDropTarget = column.type !== "unassigned"`, and `apps/web/src/components/board/board.tsx:79` rejects drops onto it. Operators must either re-drag onto a different agent column or open Forgejo to clear the assignee. This story closes the loop. ## Acceptance criteria ### Frontend - [ ] Reverse the `isDropTarget` guard in `board-column.tsx` so the Unassigned column accepts drops. - [ ] `handleDrop` in `board.tsx` calls the existing `assignCard` mutation with `assignee: null` when the target column is the Unassigned synthetic. - [ ] Optimistic update moves the card immediately; the existing rollback path (TanStack Query mutation `onError`) restores the source column on failure. - [ ] Drag-from-Unassigned-onto-Unassigned is a no-op — early return before any API call, no visual flicker. - [ ] If the card has a **running** task on the previous agent, show a confirm dialog (`AlertDialog`) before completing the drop. Dialog copy: `Cancel running task on @{previousAgent} and unassign?` with `Confirm` / `Keep assignment` actions. - [ ] On confirm, the assignment mutation calls `POST /board/assign { assignee: null, cancel_running: true }` (extend body — see backend section). ### Backend - [ ] `POST /board/assign` accepts `assignee: null` and clears the Forgejo assignee via `PATCH /repos/:owner/:name/issues/:index` with `{ assignees: [] }`. - [ ] When body includes `cancel_running: true`, cancel the in-flight task on the previous agent (mirror `/board/reroute`'s cancellation logic) and post an audit comment on the issue: `Unassigned by @{actor} via board (running task cancelled).` - [ ] When body omits `cancel_running` but the issue has a running task, return `409 { error: "running_task_present", running_agent: "<login>" }` so the frontend can prompt. ### Tests - [ ] `board.test.tsx`: drag from `dev` column to `Unassigned` → `assignCard` called with `assignee: null` + cache patch. - [ ] `board.test.tsx`: same drag with running task → 409 → confirm dialog → second call with `cancel_running: true`. - [ ] `board.test.tsx`: drag-from-Unassigned-onto-Unassigned → no API call. - [ ] Server test for `/board/assign`: `assignee: null` clears Forgejo assignee + (when `cancel_running`) cancels task + posts audit comment. ## Out of scope - Drop-to-unassign on issues that are not `type:user-story` (server filter unchanged). - Multi-card drop-to-unassign — covered by B3 (multi-select stack-drag). - Per-instance unassignment — out of scope until per-instance columns ship. ## References - Spec: `docs/specs/board-rework.md` §5 B1. - Current board route: `apps/web/src/routes/planner.board.tsx`. - Drag handlers: `apps/web/src/components/board/board-column.tsx`, `board.tsx`. - Existing assign API: `apps/server/src/domain/views/board.ts` (`POST /board/assign`, `POST /board/reroute`). - Original board spec: M18-7 / #168. ## Suggested first commit `feat(board): drop-to-unassign clears assignee in one gesture`

claude-desktop added the

area:dashboard

type:user-story

labels

2026-04-27 00:04:12 +00:00

dev was assigned by claude-desktop

2026-04-27 00:04:44 +00:00

claude-desktop added this to the v1-board-rework milestone

2026-04-27 00:04:44 +00:00

dev referenced this issue from a commit

2026-04-27 00:20:44 +00:00

feat(board): drop-to-unassign clears assignee in one gesture

dev referenced this issue from a pull request that will close it,

2026-04-27 00:20:55 +00:00

feat(board): drop-to-unassign clears assignee in one gesture #418

dev referenced this issue from a commit

2026-04-27 01:14:02 +00:00

feat(board): drop-to-unassign clears assignee in one gesture

dev referenced this issue from a commit

2026-04-27 02:20:41 +00:00

feat(board): drop-to-unassign clears assignee in one gesture

dev referenced this issue from a commit

2026-04-27 02:39:04 +00:00

feat(board): drop-to-unassign clears assignee in one gesture

code-lead closed this issue

2026-04-27 03:17:23 +00:00

code-lead referenced this issue from a commit

2026-04-27 03:17:24 +00:00

feat(board): drop-to-unassign clears assignee in one gesture

No Branch/Tag specified

main

chore/sync-pre-push-from-forge-base

fix/flows-yaml-dispatch-identity

feat/board-tap-to-assign

dev/1107

code-lead/1106

code-lead/1108

dev/1104

code-lead/1103

code-lead/1080

dev/1087

feat/flows-yaml-ci-events

chore/board-drop-stalled-and-density-controls

fix/flows-yaml-routes-always-register

flows-yaml/api-defaults

dev/1023

fix/event-log-history-bleed

fix/janitor-fix-ci-logs-and-cap

dev/1022

fix/board-card-provider

code-lead/1036

dev/1025

code-lead/1020

dev/1017

code-lead/1026

feat/web-shortcut-registry-1018

dev/1015

code-lead/1009

code-lead/1008

dev/975

dev/969

dev/973

dev/967

code-lead/968

code-lead/953

dev/970

dev/976

code-lead/966

code-lead/956

code-lead/951

dev/962

dev/963

dev/977

dev/955

dev/983

dev/961

dev/974

code-lead/950

code-lead/939

dev/941

dev/940

dev/937

dev/938

dev/936

dev/935

feat/web-i18n-fr-locale

feat/spec-editor-ui-polish

chore/drop-legacy-compat

fix/skills-drop-preview-pane

fix/882-skills-safety-rail

dev/911

dev/909

dev/923

dev/917

dev/915

feat/879-sr11-m2-drop-legacy-skill

code-lead/873

dev/881

code-lead/869

dev/867

code-lead/845

code-lead/843

code-lead/844

dev/837

dev/861

dev/849

code-lead/837

code-lead/842

fix/dedup-rebase-inflight

dev/838

code-lead/847

dev/833

code-lead/848

pr/838

code-lead/841

feat/settings-save-bar/836

code-lead/840

dev/846

code-lead/839

dev/832

fix/board-sse-stale-cache

dev/834

dev/835

feat/settings-breadcrumbs

feat/forge-oauth-credentials

refactor/service-config-consolidation

feat/agent-tokens-to-secrets

feat/gitlab-oauth-to-db

feat/authelia-rip-and-voice-fixes

fix/rebase-storm-and-dead-letter

code-lead/797

code-lead/796

dev/811

code-lead/798

dev/810

code-lead/795

dev/808

code-lead/794

dev/805

dev/802

dev/803

feat/avatar-menu-settings-entry

feat/per-agent-token-tracking

dev/793

dev/747

dev/752

code-lead/790

code-lead/759

dev/756

dev/760

dev/741

dev/767

dev/740

dev/709

dev/644

dev/637

boss/614

dev/600

dev/611

dev/585

fix/login-bonus-fixes

boss/544

dev/542

refactor/api-prefix-and-session-gate

dev/489

boss/531

boss/518

dev/499

boss/516

dev/530

dev/517

dev/519

dev/515

dev/522

dev/503

dev/471

boss/329

dev/417

dev/418

dev/402

boss/327

dev/334

dev/332

boss/326

boss/325

dev/331

boss/324

boss/323

boss/322

dev/294

test/s11-task-analytics

dev/262

boss/270

dev/268

foreman/ui-consolidation-spec

dev/234

boss/196

boss/176

boss/164

fix/124-session-persist-bind

boss/52

dev/87

boss/73

dev/77

dev/81

dev/82

boss/79

dev/42

dev/35

boss/7

No results found.

Labels

Clear labels

area:agents

Agent types, pool scheduling, per-instance config

area:dashboard

Dashboard UI and observability surfaces

area:database

DB layer — schema, migrations, ORM, raw SQL

area:design

UI/UX mockup work — routes to designer agent

area:design-review

Design review dispatch — routes to design-reviewer agent

area:flows

Flow runner — YAML loader, executor, op registry, expression eval

area:infra

Deployment, isolation, containers, systemd units

area:meta

Tracking, scaffolding, project setup

area:security

Security — routes to reviewer-security (opus)

area:sessions

Session-id store, Claude SDK resume logic

area:webhook

Forgejo webhook routing and handlers

area:workdir

Clone cache, worktrees, git identity

security

Security-sensitive issue

Tracking or decisions, not implementation work

No labels

Milestone

Clear milestone

No items

No milestone

v1-board-rework

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

dev

1 participant

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

charles/claude-hooks#409

Reference in a new issue

Repository

charles/claude-hooks

Title

Body

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?

Rows
Columns