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 using Plans.
This page refers to the advanced planning features that 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 projects. 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.
By default, Jira Software comes with Epic as a level 1 issue type, and Story as a level 0 (subtasks are considered -1 or below Story). As part of your Jira Software Premium and Enterprise subscriptions, you can add levels above 1 and use these extra levels to track your organization’s larger initiatives in your plans and unify cross-project work. Some common issue types are Legend, Odyssey, or Anthology. Or maybe you wanna go crazy and name your higher hierarchy levels things like Monolith, Deity, or Omnipotence. It’s truly up to you.
Before you can plan with levels above epic, an administrator needs to first associate the hierarchy level in your plan with a Jira issue type. This is because your plan 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:
Changes to the hierarchy settings will apply to all existing plans using this issue scheme.
1. Create issue type
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
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. Associate the issue type to your hierarchy
Now that you’ve created the issue type and added it to your issue type scheme, select Issue type hierarchy from the menu on the left.
The menu on this screen lets you arrange Jira issue types by hierarchy levels. The left column, labeled Level name, is the hierarchy structure in your plan 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 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 your plan, 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.
Was this helpful?