Jira Related Issues: A Practical Guide to Linking Work Items
Missing Jira work dependencies? Learn how jira related issues link blockers, duplicates, and related work. Read now to link smarter.
A bug blocks a release, but its Jira issue sits apart from the feature it affects. Teammates may miss the dependency, duplicate investigation, or close work in the wrong order.
That’s what related-issue links help prevent. They connect work items so you can see dependencies, duplicates, blockers, and other relationships directly in Jira. But here's the truth: adding a link is easy; choosing the right relationship and keeping links useful takes a little care.
This guide walks you through linking Jira issues, choosing relationship types, and avoiding common mistakes. You’ll also see how clear linking conventions can make project tracking easier across a team.
How to Link Related Issues in Jira
Jira issue links connect one work item to another and label how the two items relate. You can usually add a link from an issue’s actions menu, select a relationship, and enter the other issue’s key.
Open the issue you want to link. For example, open a bug that may block a planned feature. Confirm you are working in the correct project and issue.
Find the linking action. Look for “Link” or “Link issue” in the issue’s actions menu. The menu location and wording can differ between Jira versions and project types.
Choose a relationship type. Select a label that describes the connection, such as “blocks,” “is blocked by,” “duplicates,” or “relates to.” The available options depend on your Jira configuration.
Enter the other issue. Type its issue key, such as APP-248, and select the matching result. Check the summary before continuing so you don’t connect the wrong work items.
Confirm the link. Submit the action, then inspect the issue’s linked-work section. Make sure the other issue appears with the intended relationship.
Check the relationship from both sides. Some link types have a reciprocal label. A link shown as “blocks” on one issue may appear as “is blocked by” on the other.
Here’s why: a link type can communicate more than a simple association. If a release task is “blocked by” a security fix, the team can see the dependency without relying on a comment or memory.
Choose a Link Type That Describes the Work
The relationship label tells teammates what to do with the connection. Choose the closest available match, rather than using “relates to” for every situation.
Use dependency links for blockers
Use “blocks” or “is blocked by” when one issue must move before another can progress. For example, a database migration may block a feature rollout until testing is complete.
These links help teams see sequencing needs during planning. They also clarify why an issue is waiting, which is more useful than a vague status or an old comment.
Use duplicate links to connect repeated work
When two issues describe the same bug, mark one as a duplicate of the other if your team’s process supports that choice. Keep the issue with the clearest details or active work as the primary item.
For example, a customer report and a testing-team report may describe the same login failure. Linking the duplicate preserves visibility while helping the team avoid investigating the same problem twice.
Use general links when there is no dependency
Choose “relates to” for a meaningful connection that does not imply order, duplication, or containment. A design task and a technical research task might be related while progressing independently.
The best part? A precise label makes the relationship understandable even to someone who was not part of the original conversation.
Understand Issue Links, Subtasks, and Dependencies
Related issues, subtasks, and dependencies can all connect work, but they answer different questions. Picking the right structure helps your project view stay clear as work grows.
Issue links connect separate work items
An issue link describes a relationship between separate issues. The items can belong to different projects, teams, or work streams, depending on your permissions and Jira setup.
For example, a platform bug might block a mobile-app feature. Linking the issues makes the connection visible without turning one issue into a child of the other.
Subtasks divide work within a larger issue
A subtask is a smaller piece of work organized under a parent issue. Use one when the work is part of completing that parent, such as separate testing and implementation tasks for a feature.
Use a link instead when the items need to remain independently managed. A bug affecting several features may be related to each one without belonging beneath any single feature.
Dependencies describe order, not ownership
A dependency link communicates that one item must happen before another can proceed. It does not automatically assign an owner or define the complete work plan.
For instance, a team may link a compliance review as blocking a launch task. The teams still need to agree on responsibility, timing, and completion criteria.
Create Linking Conventions Your Team Can Follow
Clear conventions make issue links easier to interpret across projects. A short team agreement can reduce inconsistent labels and links that no longer help anyone make a decision.
Agree on when to link
Decide which relationships deserve a link. Your team might link blockers, duplicates, shared release dependencies, and closely related investigations, while leaving casual mentions in comments.
For example, link a bug to a feature when it affects delivery or testing. A brief mention of the feature in a discussion may not need a formal relationship.
Write a useful issue summary
A link points to an issue, so the issue’s summary should make sense outside its original conversation. “API timeout on checkout” is more informative than “Problem from testing.”
Useful summaries help people understand the connection before opening another issue. Add acceptance details or context to the issue itself when the relationship needs explanation.
Review links when plans change
Issue relationships can become stale after scope changes, closures, or team handoffs. Review important links during refinement or release planning, especially when a blocker has been resolved.
Let me explain: a closed blocker may still be useful history, but an obsolete dependency can mislead someone reviewing current work. Update or remove links when they no longer reflect the team’s understanding.
Find and Maintain Linked Work
Adding links is only helpful if teammates can discover and interpret them later. Make linked work part of routine planning and issue review, rather than treating it as a one-time cleanup task.
Check linked issues during planning
Before committing to a sprint or release, review blockers and dependencies attached to the work. If a key dependency has no owner or target date, raise that uncertainty before it affects delivery.
For example, a mobile release may depend on an API change owned by another team. Seeing the link during planning gives both teams a chance to coordinate the sequence.
Use search and reporting where available
Jira search and reporting options can help you locate linked work, though available functions depend on your Jira setup and permissions. Use them to spot issues waiting on blockers or to review dependencies across a release.
Start with a narrow question, such as “Which open issues are blocked?” A focused view is easier to act on than a broad list of every connected issue.
Keep link relationships meaningful
More links do not automatically create better visibility. Avoid connecting issues merely because they share a project, component, or broad theme.
You might be wondering: should every related issue be linked? Add one when the relationship helps someone understand priority, ownership, sequencing, duplication, or impact.
A Jira Related-Issues Solution: ONES.com
ONES.com is a unified project management and knowledge management platform powered by ONES Assistant. ONES Project handles project work and offers a Jira alternative, while ONES Wiki supports knowledge management as a Confluence alternative; they are sold separately.
For teams that need to manage linked work across projects, ONES Project includes Jira-compatible workflows, custom workflows and fields, sprint management, automation, and built-in reporting. Those capabilities can help teams represent dependencies consistently and follow linked work through planning and delivery.
Core capabilities for connected project work
Disconnected work tracking → Jira-compatible workflows → Teams can use familiar workflow patterns while organizing related work in ONES Project.
Unclear process differences → Custom workflows → Teams can shape issue transitions around how blockers, reviews, and delivery stages are handled.
Inconsistent issue details → Custom fields → Teams can capture the project information they need to clarify ownership, impact, or release context.
Limited sprint visibility → Sprint management → Teams can plan work and review linked items as part of sprint activity.
Repeated manual steps → Automation → Teams can automate selected workflow actions and reduce routine administration.
Hard-to-review progress → Built-in reporting → Teams can review project status without relying only on individual issue updates.
Plugin-heavy setups → Native capabilities → Teams can reduce reliance on extra plugins for supported project management needs.
Deployment constraints → Four deployment options → Teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment. Cloud and self-hosted versions have full feature parity.
Where teams may apply it
Cross-team release planning: A product team can track a feature alongside a platform dependency and use workflows to make review and release stages visible. Built-in reporting can help project leads check progress across the plan.
Restricted-network project work: A team with strict hosting requirements can evaluate ONES Project’s On-Premise, Private Cloud, or Air-gapped deployment options. The deployment choice does not mean giving up feature parity with the cloud version.
ONES.com offers a free plan for up to 30 seats. Teams can assess whether ONES Project fits their issue tracking and workflow needs, including whether its Jira-compatible approach supports their existing practices.
Common Challenges When Linking Jira Issues
Choosing the wrong relationship: A “relates to” link may hide a real blocker. Agree on what each relationship means, then use dependency labels when order matters.
Linking the wrong issue: Similar summaries can lead to mistakes. Confirm the issue key and summary before saving the relationship.
Creating too many links: Excessive connections make it harder to spot important dependencies. Link issues when the relationship supports a concrete decision or action.
Leaving stale blockers in place: Old links can make completed work look stuck. Review important dependencies during sprint or release planning and update them when circumstances change.
Assuming a link assigns responsibility: A relationship shows how issues connect, but it may not clarify who owns the next step. Add an assignee, deadline, or explicit coordination note when needed.
FAQs About Jira Related Issues
What does “relates to” mean in Jira?
“Relates to” indicates that two issues have a meaningful connection without stating that one blocks, duplicates, or contains the other. Use it when teammates benefit from seeing the association, but the relationship does not determine work order. For example, two issues might concern the same feature area while remaining independently actionable. If one issue prevents progress on the other, choose a dependency relationship instead.
Can Jira issues from different projects be linked?
In many Jira setups, you can link issues across projects, provided you have the necessary permissions and can access both issues. Enter the other issue’s key when creating the link, then confirm the selected result and relationship. Project settings, permissions, and available link types can affect what you can do. If the issue does not appear, check its key and your access before assuming linking is unavailable.
Do issue links change an issue’s status automatically?
An issue link generally describes a relationship; it does not by itself mean that either issue’s status will change. Jira automation or customized workflows may be configured to respond to certain events, but behavior depends on your project setup. Check your team’s workflow rules before expecting a blocker to update another issue automatically. Make ownership and next steps clear even when an automation is in place.
What is the difference between a Jira issue link and a subtask?
An issue link connects separate work items and describes how they relate. A subtask is organized under a parent issue as part of that parent’s work. Use a subtask when a piece of work belongs within a larger task. Use an issue link when items need a relationship but should remain independently managed, such as a bug that blocks a feature across another team’s project.
Can I remove a Jira issue link?
Usually, you can remove an issue link from the issue’s linked-work area, subject to your permissions and Jira configuration. Before removing it, check whether teammates rely on the relationship to understand a blocker, duplicate, or release dependency. If the connection is no longer active but still matters as history, consider whether your team should preserve the relationship or explain the change in an issue comment.
Conclusion
Jira issue links connect work items and explain whether they block, duplicate, or simply relate to each other. To create useful links, choose the right relationship, confirm the issue key, and review important connections as plans change.
When links are unclear or stale, teams can miss dependencies and spend time repeating work. A few consistent conventions can make those connections easier to trust and act on. If your team is comparing project management approaches, ONES Project is a Jira alternative with Jira-compatible workflows, reporting, and multiple deployment options.