Set up Jira Software Cloud
Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Common Jira Software configurations for 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.
Once you have access, you can begin planning with Advanced Roadmaps straight away. Nothing is stopping you. But while Advanced Roadmaps doesn’t require any customization, administrators have the power to configure it to align with Jira Software and how their teams work.
The processes described in this section are only possible with the Jira Software Administrator permissions.
Team-managed projects in Advanced Roadmaps
Advanced Roadmaps now supports team-managed projects!
We’re building out more support for team-managed projects. Learn more about what functionality is available in our docs.
As we release improvements to team-managed project support, we’ll post updates on the feature request ticket. View the feature request ticket.
Advanced Roadmaps actions in Jira Software audit logs
Administrators can track some actions in Advanced Roadmaps in the Jira Software audit logs. The following actions are included in your audit reports:
when a plan created or deleted
when scheduling configurations are changed
when issue sources are added or removed, and;
when an exclusion rule is changed
rename, create, or delete a hierarchy level
move an issue type between hierarchy levels
These can’t be edited or changed.
Learn more about how a Jira Software Administrator can audit activities.
Configure hierarchy levels above epics
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.
Jira Software, including Advanced Roadmaps, 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 subscription, you can add levels above 1 and name them to match how your organization works. 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.
Find out how to configure custom hierarchy levels in Jira for Advanced Roadmaps
Add custom fields to your Jira issues
Some default fields used in Advanced Roadmaps like Parent aren’t default fields in Jira Software. Outside of that, your organization might plan using custom date fields or labels. As such, most Jira administrators add at least one custom field to their Jira tickets when working with Advanced Roadmaps.
If you decide not to add them to your Jira issues but still use them in Advanced Roadmaps, you won’t be able to save values assigned to these fields to your issues.
The full value of custom fields will become more apparent as we cover teams later on in this guide. But for now, just know that this is a customization that you (or your Jira administrator) have at your disposal.
Was this helpful?