Dependencies

Dependencies express order between tasks: when one task can only start after another is finished. You add the prerequisites on the task that depends on them, and while any prerequisite is still open that task shows as blocked. When the prerequisites are done, it unblocks on its own. This page shows how to add a dependency, what blocked means, and where dependencies appear.

Each task carries a "Depends on" list — its prerequisites. The direction is always the same: you open the task that has to wait and point it at the tasks that must come first. There is no separate "blocks" field to fill in; a task being a prerequisite is just the other side of the same link.

Add a dependency

Dependencies live in the card details, in the "Depends on" section. Only tasks from the same project can be chosen — each project is independent.

1Open the task that has to wait for another (the dependent task).
2Find the "Depends on" section in the card details.
3Use the "Add dependency" picker to add a prerequisite task; repeat to add more than one.
4Each prerequisite appears as a chip; remove one with the x on the chip.

The picker only lists valid prerequisites. It hides the task itself, its own subtasks, tasks already added, and anything that would create a loop — so you cannot make A depend on B while B depends on A.

Dependencies are scoped to one project. You cannot make a task depend on a card that lives in another project.

Subtasks never appear as candidates because a parent waiting on its own child could never be finished. Subtasks themselves can be nested — a subtask can have subtasks of its own, up to 6 levels deep.

Blocked tasks

A task is blocked while at least one of its prerequisites is not done yet. As soon as every prerequisite reaches the done status, the task unblocks automatically — there is nothing to toggle by hand.

A blocked task shows a lock badge labelled "Blocked". Hover it to see "Blocked by" followed by the prerequisites still holding it up, so you know exactly what to finish first.

Blocked is a soft block: you can still complete a blocked task if reality got ahead of the plan. It is just never silent — the completion toast warns you, naming the prerequisite that is still pending.

Archiving a prerequisite does not clear the block. Archiving is not the same as completing: an archived task that is not marked done still counts as an open prerequisite. Mark it done to unblock the dependent task.

You can also focus on what is stuck: the "Filters" panel includes a "Blocked" filter, so you can narrow any view down to just the blocked tasks. See the "Views" page for how views and filters work.

See dependencies

The Timeline view is where the chain becomes visual. Tasks are drawn as bars over time, and dependencies are shown as arrows pointing from each prerequisite to the task that waits on it, so you can read the whole sequence at a glance.

In the Timeline, a blocked task also carries a small lock icon next to its name, matching the blocked badge you see on the task cards. See the "Task cards" page for the card details where dependencies are edited.

Dependencies never move a task on their own — they do not shift dates or change status. They only mark a task as blocked and draw the link. You keep control of scheduling and of when each task is done.

Projects created from a template or generated with AI can already come with dependencies between their example cards — edit or remove them like any other. See the "Templates and AI" page.