Jira link types describe the relationship between two work items, also called issues. Use blocks / is blocked by for a prerequisite, duplicates / is duplicated by for duplicate work, and relates to for a useful association that does not imply an order. Always read the relationship from the work item you have open.
The examples below are illustrative. Your Jira administrator can customize the available link types, so your site may use different names.
Which Jira link type should you use?
| Relationship | Example | Use it when |
|---|---|---|
| blocks / is blocked by | API-12 blocks WEB-34 | The web task needs the API work first. |
| duplicates / is duplicated by | BUG-52 duplicates BUG-41 | Both reports describe the same problem. |
| relates to | DOC-18 relates to WEB-34 | The documentation is useful context, with no prerequisite implied. |
| clones / is cloned by | TASK-29 clones TASK-10 | You want to record that one item was copied from another. |
A link records a relationship. It does not, by itself, close a duplicate, move a status, or enforce a workflow rule. Agree on what the relationship means and handle any required status changes separately. Atlassian describes this distinction in its work item linking guidance.
Blocks vs is blocked by: read the sentence both ways
Imagine that API-12 delivers an endpoint and WEB-34 builds the screen that uses it. The team cannot finish WEB-34 until the endpoint is ready.
From API-12: API-12 blocks WEB-34.
From WEB-34: WEB-34 is blocked by API-12.
These are two descriptions of the same relationship. You do not need a second, reversed link. Before saving, say the sentence aloud using the current item’s key, the selected description, and the target key. If it says the screen blocks the endpoint, but your team needs the endpoint first, the direction is wrong.
Jira stores link types with a name plus inward and outward descriptions. That is why the wording changes when you view the relationship from the other end. Atlassian’s issue linking model explains the underlying structure.
Relates to vs duplicates: context is not the same as repeated work
Suppose support files BUG-52 about the same checkout failure already tracked in BUG-41. Use duplicates from BUG-52 to BUG-41, then follow your team’s duplicate-resolution process. Linking the reports is not a substitute for deciding which ticket owns the fix.
Now suppose DOC-18 covers the checkout setup instructions. It may relate to the fix without being a duplicate or a blocker. A useful check is: “Could both tasks still proceed independently?” If yes, a general relationship may be more accurate than a blocking link.
How to add a link in Jira Cloud
On the board, open a work item’s more-actions menu and choose Link work item. Select the relationship and target item, then confirm with Link. In the detail view, the linking option is also available through the Add quick-add control. Jira is rolling out interface changes, so the labels on your site may differ. See the current Atlassian linking instructions.
After saving, open the target item and check that the reciprocal wording makes sense. If the linking option is unavailable, ask your administrator to check whether linking is enabled and whether you have the required permissions.
Are “depends on” and “is depended on by” standard link types?
Do not assume every Jira site has those labels. An administrator can define custom link types and their two directional descriptions. If your team uses “depends on,” document which end is the prerequisite and check how your planning tools interpret that type. Atlassian explains the settings in Configure work item linking.
Why a link may not appear on the project timeline
A project or space timeline displays Blocks dependencies within that project. A “relates to” link or a custom type is not automatically a timeline dependency. Atlassian documents the timeline’s dependency scope. For planning across teams and projects, read our Jira dependency management guide, which distinguishes project timelines, Plans, and issue-level views.
Keep link choices consistent across your team
Start with a short convention: blockers use Blocks, duplicate reports point to the ticket that owns the work, and related context uses Relates. Review a few real examples with the team before adding more types. A longer menu is only useful if people can reliably choose from it.
If different projects need different choices, Advanced Link Manager for Jira provides project-level link-type controls and views for managing linked work inside an issue. See our guide to controlling Jira link types per project and the setup documentation to decide whether it fits your process.
Try Advanced Link Manager for Jira to give your team clearer link choices and review dependencies where they work.
