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.
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.
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 roadmap that’s included in all Jira Software plans. Go to the documentation for project-level roadmaps in Jira Software.
The processes described in this section are only possible with the Jira Software Administrator permissions.
One key feature of Advanced Roadmaps is the ability to add hierarchy levels above epic. You can use these extra levels to track your organization’s larger initiatives in your plans and unify cross-project work.
In this documentation, we generally refer to the level above epic as initiative, but you can add as many layers as necessary. You can name these levels according to your organization’s naming structure, or use some of these common titles: Legend, Odyssey, or Anthology. You can also have some fun with it and name levels things like Monolith or Omnipotence. It’s truly up to you.
Before you can plan with levels above epic, an administrator needs to first associate the Advanced Roadmaps hierarchy level with a Jira issue type. This is because Advanced Roadmaps uses its own hierarchy structure which correlates to, but is independent from, the order of Jira issue types defined in your issue type scheme.
Adding a new custom hierarchy level is a three step process. If the issue type already exists and is part of your project’s issue type scheme, skip to step 3 of this process:
Changes to the hierarchy settings will apply to all existing plans using this issue scheme.
1. Create issue type in Jira Software
Select > Issues.
In the left column, go to Issue types > Add issue type.
Enter a name and description for your new issue type.
Choose between a standard or sub-task issue type.
Standard issue types are placed above the epic level (commonly Initiative and Legend) whereas Sub-task issue types are underneath the Story level alongside subtasks.
2. Add issue type to scheme in Jira Software
Select > Issues.
From the left column, select Issue type schemes.
Find the relevant issue type scheme and click Edit.
Edit the name, description, default issue type, and selected issue types.
To add an issue type to the scheme, drag it from Available Issue Types to Issue Types for Current Scheme. The order in which they’re listed in this box represents the hierarchical structure within Jira Software. For example, if you add the issue type bug below story, Jira will consider story to be its parent issue type.
When you’re done, select Save.
3. Add custom hierarchy levels to your Advanced Roadmaps plan:
Now that you’ve created the issue type and added it to your issue type scheme, select> Products, then select Advanced Roadmaps hierarchy configuration from the menu on the left.
The menu on this screen lets you correlate Jira issue types to hierarchy levels in Advanced Roadmaps. The left column, labeled Level name, is the hierarchy structure in Advanced Roadmaps and the right column, labeled Jira issue types, are the configured issue types in your scheme.
To add a new level, select + Create level at the bottom of the menu. Give your new Advanced Roadmaps level a name, then use the dropdown in the Jira issue types column to associate it with an issue type.
To reorganize your hierarchy structure, drag and drop the levels into the order you’d like. The order of this list is how your hierarchy levels will show in Advanced Roadmaps, and won’t change the structure of your Jira issue types as previously configured.
Once you’ve configured your level, select Save changes.
On your Roadmap view, adjust your hierarchy filters in the Filters menu to include your new hierarchy level on your timeline.
In order to see custom hierarchy level relationships in Jira Software issues, you must add the Parent field to your issues.
Grab some coffee, take a victory lap, and high-five someone. You’ve made it to the end!
Was this helpful?