Refine the dependencies view of your plan
This page refers to the advanced planning features that are only available as part of Jira Cloud Premium and Enterprise.
In the Dependencies view of your plan, you can choose which work items show and how they appear.
Parent work item and child work item are relative terms used to refer to higher-level work items that contain smaller tasks. This concept scales to any hierarchy level:
an initiative (parent work item) that contains epics (child work item)
an epic (parent work item) that contains stories (child work item)
a story (parent work item) that contains subtasks (child work item)
In this documentation, we use initiative, epic, and story in examples to refer to hierarchy levels based on Agile best practices. However, in Jira these labels can be configured by your administrator.
Filter work items
Show or hide work items from your Dependencies view based on
the Project they’re in
Sprint assignment
a specific work item or
work item link type (if configured by your administrator)
Roll-up to
Choose at which hierarchy level you would like to see your dependencies – whether you’d like to see the individual story-level work items, or how this relationship impacts the parent work items.
If you choose to view your dependencies up to levels above the dependent work items, it shows as a dotted line to indicate that the dependency being referenced is not of the same hierarchy level as your current view. Select the x links text above the dotted arrow to reveal the specific work items which are dependent on each other.
Group by
You can group dependencies based on:
Team
Sprint
Project
Parent level work items (such as Epic)
You can only group by the parent-level work items above story in your site. For example, if your Stories roll into Epics which roll into Initiatives, you’ll only be able to group by Epics.
When grouping by the parent-level task, subtasks are automatically rolled up into the Story-type level.
Was this helpful?