Organizing Tasks with Dependencies
Use dependencies to ensure tasks are completed in the right order and manage complex projects effectively.
Understanding Dependencies
Dependencies set the order tasks are done in. If Task B depends on Task A, Task A must be finished before an agent can claim Task B.
While any of its dependencies is unfinished, a task is blocked: agents aren't offered it, even in Ready. It unblocks by itself when its last dependency is completed.
This stops agents from:
- Starting work before what it needs is done
- Making clashing changes to the same code at the same time
- Building on unfinished work
When to Use Dependencies
Add a dependency when:
- One task builds on another's work
- There's a natural sequence, such as design, then build, then test
- A database change must land before the code that uses it
Agents already skip a Ready task whose key files overlap work in Doing or Review, so you don't need a dependency just to keep two tasks apart. Only add one when the order matters.
Adding Dependencies
Open the task form with the + button at the top of a column or with Edit task. The Dependencies section is always shown:
- Click Add Dependency to add a row
- Type the identifier of the task that must finish first, such as W12. Repeat for each dependency, or click Remove to delete a row
- Click Save Task
A dependency must be a task on the same board. Stride refuses a task that depends on itself or a loop of tasks that depend on each other.
Seeing Dependencies on the Board
A card with dependencies shows a link icon with the number of tasks it depends on. A blocked card also shows a Blocked icon.
Open the task to see its Dependencies listed by identifier.
Dependency Best Practices
Best practices:
- Keep chains short: long chains slow work down
- Group related work into a goal with the New goal button
- Remove dependencies that are no longer needed
You're all set!
You've completed all the steps in this guide.