How to Track Dependencies in Linear (Step-by-Step)
Linear takes a lightweight approach to dependency tracking with issue relations and sub-issues. Its dependency features match its philosophy: simple, visible, and actionable.
This guide covers using these features effectively.
Step-by-step guide
Step 1: Use blocks/blocked-by relations
Add a relation choosing "Blocks" or "Is blocked by." Linear displays a warning icon on blocked issues.
Step 2: Use sub-issues for implementation order
Break large issues into sub-issues ordered by implementation sequence.
Step 3: Create a blocked issues view
Create a saved filter: Status is not Done AND Has relation "Is blocked by." Pin to sidebar.
Step 4: Use Projects for cross-team coordination
Group related issues across teams in a Linear Project with milestones for coordination checkpoints.
Step 5: Review in cycle planning
Filter for blocked issues. Confirm blockers will be resolved before the issue is needed.
Common mistakes
Using "relates to" for dependencies
"Relates to" does not show blocking warnings. Use "Blocks" / "Is blocked by" for actual dependencies.
Too many dependencies
If every issue has 3+ dependencies, stories are probably too coupled.
Not resolving proactively
Blocked issues sitting quietly kill velocity. Review the blocked view daily.
Tips
- Set up Slack notifications for when blocking issues complete
- Use Linear triage to catch dependency issues before cycle start
- Review blocked issues at every standup
How Vantage helps
Vantage generates dependency-aware tickets that map directly to Linear issue relations. When pushed to Linear, "blocks" and "is blocked by" relationships are created automatically.