TL;DR
Dependencies = blocking order ("B can’t be done until A is done"). Links = related items without ordering ("these tasks are related"). Use dependencies for workflow order; use links for references.
Task dependencies
Purpose: Define order of work. Task B is blocked until Task A is done.
Example: "Implement API" depends on "Design API spec." Design must be in Done before Implement can be completed.
Behavior:
- Board and reports can show blocked status
- Completion may be restricted until predecessors are done
- Often used for workflows and release planning
See: Task dependencies.
Task links
Purpose: Associate tasks without enforcing order. "Related to" or "duplicate of."
Example: "Login bug" is related to "Auth refactor." Both can progress independently.
Behavior:
- No blocking; both tasks can be worked on at once
- Useful for references, duplicates, and "see also"
- Shown as links on the task
When to use which
| Use case | Use |
|---|---|
| "B can’t start until A is done" | Dependencies |
| "These are related / see also" | Links |
| Release planning, ordered phases | Dependencies |
| Duplicates, references | Links |
| Blocking indicators on board | Dependencies |
Both on the same task
A task can have dependencies and links. For example:
- Depends on: "Design spec" (blocking)
- Related to: "Similar feature" (reference)
Next steps
Add task dependencies, understand kanban boards, or use milestones.