• Products
  • Documentation
  • Resources

Common Jira Software configurations for Advanced Roadmaps

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.

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.

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.

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 Link 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.

Learn how to add custom fields to your Jira Software issues

Additional Help