Jira Links: A Step-by-Step Guide to Linking Related Issues
Need to connect related issues clearly? This step-by-step Jira link guide helps you choose the right relationship and avoid delays. Read now.
To link related issues in Jira, open an issue, choose the link action, select a relationship, and find the issue you want to connect. The link gives your team useful context without copying the same details into multiple issues.
But here's the truth: choosing the wrong relationship can make work harder to follow. A blocked issue is different from a duplicate, and a vague link can leave teammates guessing about what happens next. As projects grow, those small misunderstandings can lead to repeated work, missed dependencies, or delays.
Here's why a clear linking habit matters: it shows how issues affect one another and helps people find the next step quickly. I’ll walk you through the Jira process, explain which link types to choose, and cover common problems so your issue relationships stay useful.
How to link related issues in Jira
Use Jira’s issue-link action to connect two existing issues. The exact menu location can vary by Jira version and project configuration, but the steps are similar.
- Open the first issue. Go to the issue that needs a relationship with another task, bug, or request.
- Find the linking action. Select
More or the issue’s actions menu, then choose Link or Link issue. Some layouts show this action elsewhere on the issue view.
- Choose a relationship type. Select a label that describes how the two issues are connected, such as
blocks, is blocked by, or relates to.
- Find the second issue. Search by its issue key, such as
PROJ-42, or enter a recognizable part of its summary.
- Confirm the link. Check that you selected the intended issue and relationship, then submit the action.
- Verify the result. Return to the issue view and check the linked issues section. Open the other issue if you need to confirm the relationship appears there too.
The link connects the issues; it doesn’t merge them or copy their content. For example, linking a bug to a release task can make the relationship visible while keeping each issue’s status and ownership separate.

Before you start
You may need permission to view both issues and link them. If the linking option is missing, ask a Jira administrator whether your role has the required permission or whether the project’s issue view uses a different menu layout.
Choose the right Jira issue link type
A link type should tell someone why two issues are connected. Choose the relationship that reflects the work, not simply the first label in the menu.
| Link type | Use it when | Example |
blocks / is blocked by | One issue must be completed before another can move forward. | A security review blocks a production release. |
duplicates / is duplicated by | Two issues describe the same underlying work. | A second bug report describes an existing login error. |
clones / is cloned by | One issue was copied to create related work that will be tracked separately. | A team creates a regional task from an existing implementation issue. |
relates to | Issues have a useful connection, but none of the more specific relationships fit. | A feature request and a research task concern the same customer need. |
Jira installations can offer different link types or labels. If the relationship your team needs is missing, ask an administrator to review the available link types rather than using a misleading label.
Distinguish an issue link from a parent-child relationship
Issue links describe connections between issues. A parent-child relationship represents work organized in a hierarchy, such as a larger item containing smaller tasks. Use the structure your project supports when one issue genuinely contains or groups another.
For example, a bug that prevents a separate feature from shipping may need a blocks link. A development task that belongs under a larger feature may need a parent relationship instead. Mixing the two can make planning and reporting harder to interpret.
Understand link direction before confirming
Some Jira relationships have a direction. If issue A blocks issue B, Jira may show the reciprocal wording on issue B: it is blocked by issue A. Both labels describe the same connection from different viewpoints.
Let me explain: start with the issue you have open, then read the relationship as a sentence. If the current issue is waiting for another task, choose the wording that says it is blocked by that task. If completing the current issue holds up another, choose blocks.
A quick example can prevent a confusing link. If APP-18 is a review that must finish before APP-31 can ship, APP-18 blocks APP-31. When you open APP-31, the reciprocal relationship may read is blocked by APP-18.
Keep issue relationships useful over time
Links are most helpful when they explain a real connection. Add them when work depends on another issue, repeats it, or needs context that teammates should be able to find quickly.
For example, a support team could link a customer-reported bug to the engineering issue tracking its fix. A product manager could link a research task to a feature request. In both cases, the relationship saves a teammate from searching manually.
Use a simple linking routine
- Choose a specific relationship whenever one fits.
- Check the issue key and summary before confirming.
- Link the relevant issues instead of adding the same explanation to several descriptions.
- Review old links when work changes, especially when a dependency is removed or a duplicate is closed.
- Explain unusual relationships in a comment if the link label alone doesn’t make the reason clear.
The best part? A short review can prevent stale links from misleading the next person. During sprint planning, for instance, you can check whether an issue marked as blocked still has an active dependency.
Troubleshoot Jira issue-link problems
If a link action fails or the relationship looks wrong, check the issue selection, link direction, and access permissions first. These are common causes, and each is usually quick to investigate.
The link option is missing
Your Jira role may not include permission to link issues, or the action may be located in a different menu in your layout. Ask a project administrator to check your permissions and confirm where the action appears for your project.
The wrong issue appears in search
Issue summaries can be similar, especially in large projects. Search with the full issue key, then verify the summary before creating the relationship. If the issue doesn’t appear, check whether you can view it.
The relationship reads backward
Directional labels can feel reversed when you start from the other issue. Read the wording from the current issue’s point of view, then confirm the reciprocal label on the connected issue. Remove and recreate the link if it describes the opposite dependency.
The link type doesn’t match the work
A generic relationship can hide an important dependency, while a blocking label can wrongly imply that progress must stop. Choose the closest accurate link type and add a brief comment when the relationship needs extra explanation.
ONES.com for connected project workflows
ONES.com brings project management and knowledge management together in a unified platform. ONES Project is its project management product and a Jira alternative; ONES Wiki provides knowledge management and is sold separately.

For teams reviewing their project workflow, ONES.com offers Jira-compatible workflows and deployment choices that include Cloud, On-Premise, Private Cloud, and Air-gapped environments. Confirm how any platform handles the exact issue-link types and relationships your team relies on before changing systems.
Core capabilities
- Pain: Teams may want to preserve familiar processes when moving away from Jira. ONES capability: Jira-compatible workflows. Result: You can map existing ways of working with less process disruption.
- Pain: Teams may struggle to see progress across active work. ONES capability: Built-in reporting. Result: Project progress is easier to review without relying on a collection of separate add-ons.
- Pain: A standard process may not fit every team. ONES capability: Custom workflows and fields. Result: Teams can adapt issue handling to their work.
- Pain: Sprint planning can become disconnected from issue execution. ONES capability: Sprint management. Result: Teams can plan and track sprint work in their project management environment.
- Pain: Repeated routine actions take time. ONES capability: Automation. Result: Teams can reduce manual steps in supported workflows.
- Pain: A growing set of plugins can add maintenance overhead. ONES capability: Native capabilities and feature parity between cloud and self-hosted versions. Result: Teams can assess core needs with fewer plugin dependencies.
- Pain: Some organizations need control over where their platform runs. ONES capability: Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: You can evaluate a deployment model that fits your environment.
- Pain: Restricted networks may not allow cloud services. ONES capability: An Air-gapped deployment option. Result: Teams can assess a project management setup for disconnected environments.
- Pain: Project activity and team knowledge can become separated. ONES capability: ONES.com includes project and knowledge management, with ONES Wiki sold separately. Result: Teams can consider both needs within the same platform family.
Application scenarios
Jira migration review: A software team can compare its current workflows, issue fields, sprint practices, reports, and issue-link requirements with ONES Project before planning a transition. That review helps the team identify which practices need configuration or further verification.
Restricted-network project work: An organization with disconnected environments can evaluate the Air-gapped deployment option alongside its workflow and reporting requirements. A team that also wants knowledge management can separately assess ONES Wiki.
ONES.com offers a free plan for up to 30 seats. Teams can evaluate whether its workflows, deployment options, and issue-link behavior fit their needs before deciding whether to change their setup.
Common challenges when linking issues
Too many loosely related links
Problem: Linking every issue that mentions the same feature makes relationships difficult to scan. Solution: Create a link when it helps someone understand a dependency, duplicate, clone, or meaningful connection. Add a short comment if the reason is not obvious.
Stale dependency links
Problem: A completed or cancelled task may remain marked as blocking work. Solution: Review dependency links during sprint planning or issue closure. Remove or update a link when the work no longer depends on it.
Confusing links with hierarchy
Problem: A related issue may be mistaken for a child task. Solution: Use a parent-child structure for work that belongs under a larger item, and an issue link for a relationship between separate issues.
Inconsistent link types across teams
Problem: Different teams may use broad or directional labels in different ways. Solution: Agree on short examples for common cases, such as blockers and duplicates, and make that convention easy for team members to find.
FAQs about Jira issue links
Can I link issues in different Jira projects?
In many Jira setups, you can link issues across projects if you can access both issues and have the required permissions. Search for the target issue by its full key to avoid selecting a similarly named issue. If it doesn’t appear or the link action is unavailable, ask a Jira administrator to check access and project settings.
Do Jira issue links change an issue’s status?
Creating a link does not, by itself, change either issue’s status. A link can show that one issue blocks another, but the team still needs to manage status changes through its workflow. Some projects may have automation rules that react to issue changes, so check your project’s configuration if you see an unexpected status update.
What’s the difference between “relates to” and “blocks”?
Relates to signals a connection without saying that progress depends on the other issue. Blocks describes a directional dependency: one issue’s completion affects another’s progress. For example, a research task may relate to a feature, while a required approval may block its release.
Can I remove an issue link?
If your permissions allow it, open the issue and find its linked issues section. Use the action beside the relationship to remove it; the exact control depends on your Jira interface. Removing a link doesn’t usually delete either issue. Check the issue details afterward to confirm the relationship is gone.
Conclusion
Linking issues in Jira is a simple way to make dependencies, duplicates, and related work easier to follow. Open an issue, select the appropriate link type, find the other issue, and verify the relationship from both sides when direction matters.
Choose labels carefully and review links as work changes. That small habit can reduce confusion, prevent stale dependencies from lingering, and help teammates understand what to do next. When your team evaluates a different project workflow, compare its issue relationships and deployment needs against the way you actually work.