This article explains how to connect related Jira work using Sub-tasks, the Parent field, and Linked work items. Understanding these relationships helps you organize work and retrieve related items with JQL.
Note: The new Atlassian Community website does not currently support images or canonical links. To ensure the original content remains intact and clearly identified, I’m posting a summary of content here. The complete article is available on my website.
Read the full article at: https://www.jirastrategy.com/linking-related-jira-work
Article Summary
Jira provides several ways to connect related work items, but the right method depends on the relationship you're trying to represent. The three main linking methods are: creating Sub-tasks, using the Parent field, and using the Linked work items function.
- Sub-tasks create a direct parent/child relationship with a Story, Bug, or Task. This is a strong relationship because Sub-tasks always have a parent. Certain operations performed on the parent also affect its children, like moving a Story with Sub-tasks into a sprint, for example.
- For higher-level relationships, use Jira's Parent field to establish hierarchy between work items. For example, connect Stories to a related Epic. Jira Cloud Premium and Enterprise also supports additional hierarchy levels above Epics.
- For relationships that don't fit neatly into a hierarchy, Jira's Linked work items feature provides more flexibility. You can link work items using relationship types like: blocks, clones, duplicates, relates to, and more.
Understanding the differences between hierarchy, dependencies, and relationships helps you organize work and access related items with JQL searches.
Read the Article
See the JQL queries and read the full article at:
https://www.jirastrategy.com/linking-related-jira-work/
