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.
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.
Add custom fields to your Jira issues
Some default fields used in Advanced Roadmaps like Labels and Components 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?