Set Up Issue Relations in Linear
Use blocking relations for sequencing, related links for context and duplicate links for the same underlying work. Relation direction matters when another team depends on you.
Step-by-step guide
Check access and scope
You need access to the linked issues and agreement with the receiving owner about the actual dependency.
Identify the prerequisite
Open the dependent issue and identify the prerequisite outcome.
Choose the relationship
Choose the relevant relation rather than placing a URL only in prose.
- Worked example: The invitation UI is blocked by the token-validation endpoint. A research interview about invite wording is related context unless the UI implementation truly cannot proceed without it.
Check link direction
Check blocking direction from both issue records. Inspect the dependent issue as blocked by its prerequisite, and the prerequisite as blocking the dependent work.
Explain the unblock condition
Add an explanation of the contract or artifact needed to unblock work.
Review with both owners
Review links during planning and remove obsolete dependencies.
Verify the result
Both issues express the intended direction and owners agree on the condition that removes the block.
Common mistakes
Avoid the main failure mode
Linking everything as blocked creates a dependency graph nobody trusts. Reserve blocking edges for a concrete unmet condition.
Check the handoff edge case
A blocking link without an agreed handoff condition can remain unresolved after its prerequisite is complete. Describe the expected artifact.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.