Kanban: column rename cascade is non-atomic — failed task migrations silently orphan cards #139

New issue

Closed

opened 2026-04-22 13:29:31 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-22 13:29:31 +00:00

Member

board_view.rs::handle_edit_swimlane saves the renamed project first, then fans out per-task move_task_to_swimlane calls via futures::future::join_all. If any of those task updates fails, the project already holds the new swimlane name but the affected task still points at the old name. The card disappears from the board (no column matches its stored swimlane string) and the error only surfaces as a banner the user is likely to miss.

Options:

Wrap the cascade in a server-side rename_swimlane RPC that atomically renames the swimlane and all tasks in one transaction (requires SDK work).
Short term: roll back project.swimlanes to the old name on any task-update failure, and re-issue the failed moves on a retry.
Also surface a persistent "N tasks failed to migrate · Retry" chip next to the renamed column instead of a transient error banner.

`board_view.rs::handle_edit_swimlane` saves the renamed project first, then fans out per-task `move_task_to_swimlane` calls via `futures::future::join_all`. If any of those task updates fails, the project already holds the new swimlane name but the affected task still points at the old name. The card disappears from the board (no column matches its stored `swimlane` string) and the error only surfaces as a banner the user is likely to miss. Options: - Wrap the cascade in a server-side `rename_swimlane` RPC that atomically renames the swimlane and all tasks in one transaction (requires SDK work). - Short term: roll back `project.swimlanes` to the old name on any task-update failure, and re-issue the failed moves on a retry. - Also surface a persistent "N tasks failed to migrate · Retry" chip next to the renamed column instead of a transient error banner.