Jira Linked Issues: A Step-by-Step Guide to Issue Linking

Unsure how to connect related tickets? Learn Jira linked issues step by step and choose the right link type to clarify dependencies. Read now.

When two Jira issues affect the same work, keeping them separate can hide important dependencies. You may miss a blocker, duplicate a task, or overlook the reason one issue changed another. That confusion grows when a project has dozens of related tickets and several people updating them.

Jira linked issues make those relationships visible, but choosing the wrong link type can create more confusion instead of less. A dependency is different from a duplicate, and a general connection does not explain which issue should happen first. Here’s the truth: a clear relationship and a consistent linking habit make tickets easier to navigate. This guide walks you through creating links, choosing the right relationship, and maintaining useful connections as your work changes.

How to Link Jira Issues Step by Step

You can link two Jira issues from an issue’s action menu, select the relationship, and identify the other issue. First, confirm issue linking is available in your Jira project.

Open the first issue. Navigate to the issue that you want to link. For example, open a bug that is preventing a feature from moving forward.
Find the linking action. In many Jira Cloud views, select More and then Link. The exact location can vary with your Jira version and issue layout.
Choose a link type. Select a relationship that describes how the issues connect. For a blocker, you might choose blocks or is blocked by.
Enter the other issue key. Add the key for the related issue, such as APP-214. Check that the issue shown is the one you intended to link.
Confirm the link. Select Link or the equivalent confirmation option. Jira should show the relationship in the issue’s linked issues area.
Verify the relationship from both sides. Open the other issue and check that the reciprocal link makes sense. For example, if one issue blocks another, the reverse view should show that it is blocked by the first.

If you can’t find a linking action, ask a Jira administrator to check whether issue linking is enabled and whether your project permissions allow the action. A short verification step helps catch mistaken issue keys before they mislead the team.

Jira product screenshot

What Jira Issue Links Mean

Issue links describe relationships between separate Jira issues. They help you see that one task blocks another, that two tickets are duplicates, or that work is connected in a less direct way.

Some link types are directional. For example, blocks and is blocked by describe the same relationship from opposite perspectives. Other types, such as relates to, indicate a connection without assigning a direction.

Here are common examples:

blocks / is blocked by: One issue must be resolved or completed before another can progress.
duplicates / is duplicated by: Two issues describe the same work or problem.
clones / is cloned by: One issue was copied to create another issue.
relates to: Issues have a useful connection, but the link does not explain a dependency or duplicate.
causes / is caused by: One issue has a causal relationship with another, where that link type is available.

For example, a payment-service defect might block a checkout improvement. Linking those tickets with a blocking relationship communicates more than simply saying they are related.

Choose a Link Type That Explains the Work

Before linking issues, ask what a teammate should understand when they see the connection. If the answer is “this work must happen first,” use a directional dependency. If both tickets describe the same defect, mark them as duplicates.

Use relates to when the connection matters but has no clear direction. For instance, a design review and a performance investigation might concern the same feature without one blocking the other.

Here’s why: vague relationships create extra interpretation. If you link two issues as related when one is actually blocked, someone scanning the issue may not realize that work is waiting.

A practical rule is to choose the most specific relationship that is accurate. If no available link type fits, use a clear issue description or team convention to explain the connection instead of forcing an inaccurate label.

Link Issues Across Projects Carefully

Jira links can connect issues that belong to different projects, which is useful when one team depends on another. For example, a mobile app task might rely on an API change tracked by a platform team.

Before creating a cross-project link, confirm that the other issue is accessible to the people who need to act on it. A relationship is less helpful when teammates cannot view the linked issue or understand its status.

Include the reason for the relationship in a comment or issue description when the link alone leaves questions. A brief note such as “Checkout testing is waiting for the API response change” gives the next person context without requiring a long investigation.

When teams use different workflows, agree on who updates the dependency and how status changes should be communicated. This keeps the relationship useful even when the issues move through separate boards or project processes.

Keep Issue Links Accurate Over Time

A link can become misleading when scope changes, a dependency is removed, or duplicate work is resolved. Review important connections during backlog refinement, sprint planning, or a dependency check-in.

For example, if a linked blocker is closed because the team chose a workaround, confirm whether the downstream issue is still waiting. Remove or update the relationship when it no longer reflects the work.

Let me explain: a well-maintained issue link acts like a small map between pieces of work. An outdated link is like a road sign pointing in the wrong direction; it can slow down the people trying to follow the project.

Teams can also agree on a lightweight linking convention. Decide which relationships need a comment, who checks cross-project dependencies, and when resolved duplicates should be reviewed.

Issue Relationship Management with ONES.com

ONES.com product screenshot

Value Proposition

ONES.com brings project management and knowledge management together in a unified platform powered by ONES Assistant. ONES Project is the project management product and a Jira alternative; ONES Wiki is the knowledge management product and a Confluence alternative. They are sold separately.

For teams evaluating another way to coordinate Jira-style work, ONES Project offers Jira-compatible workflows, custom fields, sprint management, automation, and built-in reporting. Those capabilities can help teams organize work and clarify ownership while reducing dependence on plugins.

Core Capabilities

Pain: Jira workflows are difficult to adapt. ONES Project supports Jira-compatible workflows and custom workflows. Result: Teams can shape work stages around their process.
Pain: Issue details don’t match the team’s needs. Custom fields let teams capture relevant information. Result: People can understand work without relying on inconsistent descriptions.
Pain: Sprint coordination takes repeated manual effort. Sprint management supports planning and tracking. Result: Teams have a clearer view of planned work and progress.
Pain: Repetitive actions slow down delivery. Automation can handle configured workflow actions. Result: Teams can reduce routine steps and keep work moving.
Pain: Progress is hard to review. Built-in reporting provides project visibility. Result: Teams can review status without assembling updates from multiple plugins.
Pain: Plugin-heavy setups take extra coordination. Core project capabilities are available within ONES Project. Result: Teams can reduce reliance on add-ons for common project needs.
Pain: Hosting requirements vary between organizations. ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: Teams can select a deployment that fits their operating environment.
Pain: Self-hosting can mean sacrificing capabilities. ONES.com offers full feature parity between its cloud and self-hosted versions. Result: Teams can consider on-premise deployment without giving up feature access.

Application Scenarios

Cross-functional product delivery: A product team can use ONES Project workflows, custom fields, and reporting to coordinate feature work across development and testing. A team convention can clarify how members communicate dependencies and related tasks.

Restricted hosting environments: An organization that needs an air-gapped or on-premise deployment can evaluate ONES Project while retaining access to the platform’s feature set. If the team also needs a knowledge base, it can consider ONES Wiki separately.

Common Challenges with Jira Links

The Link Action Is Missing

Problem: You open an issue but can’t find the option to link another one. Solution: Check your project permissions and ask a Jira administrator whether issue linking is enabled. The menu placement can also differ by Jira view.

The Relationship Is Unclear

Problem: A teammate sees a link but can’t tell what it means. Solution: Select a more specific relationship when possible, then add a short explanation if the reason still needs context.

The Wrong Issue Was Linked

Problem: A similar issue key or title led to an incorrect connection. Solution: Verify the issue summary before confirming, then check the relationship from both issues. Remove the mistaken link and add the correct one.

A Dependency Has Changed

Problem: The work no longer depends on the linked issue, but the relationship remains visible. Solution: Review the affected issues during planning or refinement. Update or remove links when scope, sequence, or ownership changes.

FAQs About Jira Linked Issues

Can Jira issues be linked across different projects?

Yes, Jira can link issues across projects when you have access to both issues and the relevant permissions. This is useful when work in one team depends on a task managed elsewhere. Before adding the link, check that the people who need to follow the dependency can view the other issue. Add a brief explanation if the relationship may not be obvious.

What is the difference between “blocks” and “relates to”?

Blocks communicates a directional dependency: progress on one issue is waiting for another. Relates to indicates a connection without stating that one issue must happen first. Use the blocking relationship for a genuine prerequisite, such as an API change needed before an app feature can be tested. Use a general relationship when neither issue blocks the other.

Why can’t I link Jira issues?

The linking action may be unavailable because issue linking is disabled, your permissions don’t allow it, or the action appears in a different location in your Jira view. Check the issue’s action menu first. If the option remains missing, ask your Jira administrator to review the project configuration and your access. Confirm that you are viewing an issue where you can make changes.

Can I remove or change an issue link?

You can usually remove an issue link if you have the required permissions. Open the issue, find the linked issues area, and use the available action to remove the incorrect or outdated relationship. To change the relationship type, remove the old link and create a new one with the appropriate type. Check the other issue afterward to confirm the connection now reads correctly.

Conclusion

Jira issue links help you show how work connects, especially when tasks depend on each other or describe the same problem. Open the issue, select the linking action, choose an accurate relationship, and verify the connection from both sides.

Then keep those relationships current as plans change. A few careful links can prevent overlooked blockers, reduce duplicate work, and give your team a clearer view of what needs attention. If your project coordination needs evolve, ONES Project is another Jira alternative to evaluate for Jira-compatible workflows and flexible deployment options.