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.
Create powerful rules to start automating your manual, repetitive processes.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
The Dependencies report gives you three different ways to narrow down which dependencies show in your report: Roll up to, Group by, and Filter by issue.
This feature allows you to 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 will show 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. The dotted line will turn red if your dependency structure has warnings which require your attention.
When rolled up to the epic level, you can still view which issues are linked with dependencies by selecting the x links text above the dotted arrow to show the specific issues represented.
You can also view dependencies based on the team to which they’re assigned by selecting Team from the Group by dropdown. This will group your dependencies based on their assigned team.
In the example above, IOS-13 and IOS-19 are assigned to the IOS board team while ADR-14 is unassigned.
Filter by issue
Lastly, you can Filter by issue to highlight a single issue and see a visual layout of its dependencies. In the example below, IOS-13 blocks both IOS-19 and ADR-14:
The Filter by issue function lets you focus on one specific issue and dependencies related to it, and can be accessed in two ways. The first is by using the Filter by issue dropdown at the top of the map. Alternatively, you can select Filter by this issue from the menu.
The example below shows what happens when the function is applied to only show the issues related to IOS-19:
Was this helpful?