Dependencies
Sometimes one task can’t start until another is finished — you can’t “paint the wall” before you “patch the wall”. Dependencies let you record that, so work only arrives on the board when it’s ready to do.
Blocked by / Blocks
In the task editor you’ll see a strip of dependency chips, each with a small glyph showing which way it points:
- Blocked by chips — the tasks that must be done before this one.
- Blocks chips — the tasks that are waiting on this one.
Adding a dependency
- Open a task and press + dep next to its dependency chips.
- Choose Blocked by or Blocks at the top of the sheet, depending on which way the link goes.
- Use Search tasks to find the task and pick it.
The link shows up on both tasks automatically — the blocker gains a Blocks chip pointing back. Remove a link with the ✕ on its chip.
Cycles aren’t allowed
You can’t create a loop — if task A waits on B, B can’t also wait on A (directly or somewhere down the chain). Plan afoot will stop you with “That would create a cycle”.
Seeing what’s blocked
Expand a card — the chevron in its top-right corner — and its dependencies appear around it, threaded onto one vertical line: whatever it’s blocked by above it, whatever it blocks below it. Each row carries a number for how deep that task sits in the chain, so the numbers always climb as you read downward, and the card’s own number tells you where you are in it.
Tap any row to go to that task. When a set is too long to show at once it collapses to a strip of numbered circles — tap that to page through it a few at a time, so a task with thirty dependents never buries the cards around it.