How to Link Issues in Jira: A Step-by-Step Guide for Teams
Unsure how tasks connect? Learn to create issue links in Jira, choose the right link type, and clarify dependencies. Read now to guide your team.
Have you ever opened a Jira issue and wondered whether it blocks another task, duplicates it, or simply relates to it? The right connection can clarify what your team should do next.
But here's the truth: a vague or incorrect link can send teammates in the wrong direction. Dependencies may be missed, duplicate work can continue, and a project board may tell an incomplete story. A link also does not automatically assign work or change an issue’s status.
You can connect Jira issues in a few steps by choosing the right link type and entering the related issue key. I’ll show you how to create and check those connections, when to use each relationship, and how to keep issue links useful as work changes.
How to Link Issues in Jira
To link issues in Jira, open an issue, choose the link action, select a relationship, enter the other issue’s key, and confirm. The exact menu label can vary slightly between Jira layouts, but the process is similar.
Open the issue you want to link. Find the Jira issue that will be the starting point, then open its full detail view. For example, you might open PAY-42, a payment defect that could delay a release task.
Find the linking action. Look for More, an ellipsis menu, or an issue links panel. Choose Link or Add link. If you cannot see the option, your Jira permissions or project configuration may limit access.
Choose a relationship type. Select a clear link such as blocks, is blocked by, duplicates, or relates to. The relationship should describe how the two issues affect each other, not just that they share a topic.
Enter the related issue key. Type the key, such as REL-18, into the issue field. Check the result Jira displays so you do not connect the wrong task, especially when several issues have similar summaries.
Confirm the link and inspect both issues. Click Link or the confirmation button. Review the issue links area to check the relationship. If the connection is directional, open the other issue too and confirm Jira displays the inverse relationship you expect.
Example: If PAY-42 must be fixed before REL-18 can be released, link PAY-42 to REL-18 as blocks. Jira can show the inverse relationship on REL-18 as is blocked by.
What Jira Issue Links Mean
Issue links show relationships between separate Jira issues. They help you see dependencies, duplicate reports, and related work without merging the issues or changing their individual workflows.
Here's why: each link type tells a different story. A blocks relationship indicates a dependency, while relates to is a broad connection that does not necessarily stop progress.
| Link type | Use it when | Example |
|---|
| blocks / is blocked by | One issue’s progress depends on another issue. | A deployment task is blocked by a critical defect. |
| duplicates / is duplicated by | Two issues describe the same underlying work or problem. | A customer report duplicates an existing bug. |
| relates to | The issues are connected, but neither relationship above fits. | A feature request relates to a testing task. |
| causes / is caused by | Your Jira configuration offers this relationship and one issue directly causes another. | A configuration change causes a service error. |
Available link types depend on your Jira setup. If a relationship your team needs is missing, ask a Jira administrator whether the configuration can support it.
Choose the Right Link Type for the Relationship
Start with the question your teammate needs answered. Does one issue prevent the other from moving forward? Choose a blocking relationship. Do both issues describe the same defect? Choose a duplicate relationship.
Use relates to when the connection is useful but does not imply dependency or duplication. For example, a design review and a new feature may relate to the same product area without either one blocking the other.
Let me explain: a precise link saves people from guessing. If an issue is waiting on another team, is blocked by makes that dependency clearer than a general relationship. Add a short comment when the reason for the link is not obvious from the issue summaries.
Issue Links Versus Parent-Child Relationships
Issue links connect separate issues without making one a child of the other. Parent-child relationships, such as an epic and its stories, represent a hierarchy. The distinction matters when teams organize work or report progress.
For example, link a security review to a release task if the review affects release timing. Use a hierarchy when the review task is a defined part of a larger epic and your team wants to track it as that epic’s work.
The best part? You can use both relationship types when they describe different facts. An issue may belong to an epic and also be blocked by a separate defect. Avoid using an issue link as a substitute for a hierarchy your team relies on.
Review and Maintain Your Jira Issue Links
After creating a connection, check the issue’s links section and verify the related issue key. For a dependency, confirm the direction makes sense from both sides. This quick review can catch a reversed link before it confuses sprint planning.
Links can become stale when plans change. If a blocker is resolved, confirm whether the dependent issue can proceed. If two reports turn out to describe different problems, remove or correct the duplicate connection rather than leaving misleading context.
For a team example, imagine a bug blocks a release, but a fix removes that blocker. Updating the link and adding a short status note gives the next person a clearer view of the release path.
ONES.com Solution: ONES.com
Value Proposition
ONES.com brings project management and knowledge management together in one platform, with ONES Project for project work and ONES Wiki for team knowledge. The products are sold separately, so your team can choose the capabilities it needs.
If your team is comparing Jira alternatives, ONES Project supports Jira-compatible workflows alongside built-in reporting, custom workflows and fields, sprint management, and automation.
Core Capabilities
Hard-to-follow relationships → Jira-compatible workflows → Preserve familiar issue processes while teams organize connected work.
Limited visibility into progress → Built-in reporting → Review project progress without relying on scattered status updates.
Generic task fields → Custom fields → Capture details that match how your team describes its work.
Workflows that do not fit team needs → Custom workflows → Reflect approval steps or handoffs in the team’s actual process.
Sprint planning overhead → Sprint management → Plan and follow iterative work within the project workflow.
Repeated manual actions → Automation → Reduce routine steps with rules suited to your workflow.
Separate project and knowledge spaces → ONES Project and ONES Wiki → Choose project management and knowledge management products within the same platform.
Deployment constraints → Cloud, On-Premise, Private Cloud, or Air-gapped deployment → Select an environment that fits your organization’s operating requirements.
ONES.com offers a free plan for up to 30 seats. Its cloud and self-hosted versions have full feature parity, which can help teams evaluate deployment needs without giving up feature access. Native capabilities can also reduce reliance on extra plugins for common project workflows.
Application Scenarios
Product teams managing dependencies: A team can connect development issues, release tasks, and defects, then use workflow and reporting capabilities to follow the work. Custom fields can capture details that matter to a particular project.
Organizations with deployment requirements: A team that needs an on-premise or air-gapped environment can consider those ONES.com deployment options. Its project and knowledge products can support different needs without requiring one deployment choice for every organization.
Common Challenges When Linking Jira Issues
Problem: The relationship direction feels backward. Jira displays inverse wording on the linked issue. Solution: Read the relationship from the issue you opened, then check the other issue to confirm the reverse wording describes the same connection.
Problem: The wrong issue was linked. Similar summaries can make issue keys easy to confuse. Solution: Verify the key and summary before confirming, then inspect the link after it is created.
Problem: A vague link does not explain why two issues matter to each other. Solution: Add a brief comment with the dependency or context. Keep the link type specific wherever possible.
Problem: A once-useful link is now misleading. Plans and issue details change. Solution: Review dependencies during refinement or release planning and update connections when the relationship no longer applies.
FAQs About Linking Issues in Jira
Can I link issues in different Jira projects?
In many Jira setups, you can link issues across projects if you have access to both issues and the required permissions. Enter the other issue’s full key, such as APP-16, and confirm Jira recognizes it. If Jira cannot find the issue or rejects the link, check your access or ask a project administrator about local restrictions.
Does linking Jira issues change their status?
No. An issue link describes a relationship; it does not automatically change either issue’s status or assign work. A task marked as blocked may still need a status update through your team’s workflow. If your team wants a link to trigger an action, an administrator may be able to configure automation separately.
Can I remove or change an issue link?
Usually, you can remove a link from the issue’s links area if you have the necessary permissions. To change the relationship, remove the incorrect link and create a new one with the right type. Check both connected issues afterward, especially for a directional dependency, so the updated relationship reads correctly from either side.
Why can’t I see the option to link issues?
The link action may be in a menu or issue links panel, depending on your Jira layout. It may also be unavailable because of your permissions or project configuration. Try opening the full issue view first. If the action still does not appear, ask a Jira administrator to check your access and whether issue linking is enabled for the project.
Conclusion
To link issues in Jira, open an issue, choose a relationship that accurately describes the connection, enter the other issue key, and confirm the link. Then check the result from both sides when the relationship has a direction.
Clear links make dependencies, duplicates, and related work easier to understand. If a connection becomes outdated, correct it before it creates confusion. With a little care, your team can keep Jira relationships useful and make the next step clearer for everyone.