Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Search for issues, navigate to your work, use advanced search, and work with your search results.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
This page refers to Advanced Roadmaps, which is a cross-project planning tool only available as part of Jira Software Cloud Premium and Enterprise.
We have a separate section for documentation about the project timeline that’s included in all Jira Software plans. Go to the documentation for project-level roadmaps in Jira Software.
In the Dependency report, you can change how issues render using the following
Choose at which hierarchy level you would like to view your dependencies.
In the image below, the story-level task IOS-13 belongs to the epic IOS-6 and is blocking ADR-14, another story-level task, which belongs to the epic ADR-5. Here we see that relationship without roll-up settings applied:
When rolled up to the Epic level, Advanced Roadmaps shows a dotted line to indicate that the dependency being referenced is not of the same hierarchy level as your current view. This is because while they have stories that are dependent, the epics are not dependent on each other.
You can view which issues are linked with dependencies by selecting the x links text above the dotted arrow to show the specific issues represented, as shown below:
You can also group dependencies based on:
Parent level issue (such as Epic)
When grouping by the parent level task, subtasks are automatically rolled up into the Story-type level. Issues above the parent level won’t be grouped.
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 Software, these labels can be configured by your administrator.
Use the Project, Sprint, or Issue menus to only show issues based on specific criteria.
Was this helpful?