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 issues show and how they appear.

Parent issue and child issue are relative terms used to refer to higher-level issues that contain smaller tasks. This concept scales to any hierarchy level:

  • an initiative (parent issue) that contains epics (child issue)

  • an epic (parent issue) that contains stories (child issue)

  • a story (parent issue) that contains subtasks (child issue)

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 issues

Show or hide issues from your Dependencies view based on

  • the Project they’re in

  • Sprint assignment

  • a specific issue or

  • issue 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 issues, or how this relationship impacts the parent issues.

If you choose to view your dependencies up to levels above the dependent issues, 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 issues which are dependent on each other.

Group by

You can group dependencies based on:

  • Team

  • Sprint

  • Project

  • Parent level issue (such as Epic)

    • You can only group by the parent-level issues 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.

Still need help?

The Atlassian Community is here for you.