feat: blocked task behavior and dependency visualization #61

New issue

Closed

opened 2026-03-23 22:11:24 +00:00 by barrettruth · 1 comment

barrettruth commented

2026-03-23 22:11:24 +00:00

Problem

The "blocked" status exists but has no deep integration. No way to visualize what blocks what, no automatic status transitions when blockers are resolved, and the kanban shows a "Blocked" column even when empty.

Scope

Dependency graph visualization in task detail (show what this task blocks / is blocked by)
Auto-transition: when all blocking tasks are completed, automatically move blocked tasks to pending
Blocking indicator in queue view (show if a task is blocking other tasks)
Quick "block by" action: from a task, quickly select another task as a blocker
In kanban, if a status column has zero tasks, hide it entirely and let remaining columns fill the space
Consider merging "blocked" into a visual indicator rather than a separate column (since it's auto-managed)

Technical Notes

DAG operations already exist in src/core/dag.ts
Task dependencies table exists: taskDependencies with taskId and dependsOnId
Auto-transition logic partially exists but may need to be more robust
Kanban column rendering is in src/components/kanban-board.tsx — currently hardcoded 4 columns

## Problem The "blocked" status exists but has no deep integration. No way to visualize what blocks what, no automatic status transitions when blockers are resolved, and the kanban shows a "Blocked" column even when empty. ## Scope - Dependency graph visualization in task detail (show what this task blocks / is blocked by) - Auto-transition: when all blocking tasks are completed, automatically move blocked tasks to pending - Blocking indicator in queue view (show if a task is blocking other tasks) - Quick "block by" action: from a task, quickly select another task as a blocker - In kanban, if a status column has zero tasks, hide it entirely and let remaining columns fill the space - Consider merging "blocked" into a visual indicator rather than a separate column (since it's auto-managed) ## Technical Notes - DAG operations already exist in `src/core/dag.ts` - Task dependencies table exists: `taskDependencies` with `taskId` and `dependsOnId` - Auto-transition logic partially exists but may need to be more robust - Kanban column rendering is in `src/components/kanban-board.tsx` — currently hardcoded 4 columns

barrettruth commented

2026-03-25 17:06:18 +00:00

this would likely manifest as another core view - ideate deeply and creatively on what this would look like