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.
Troubleshoot your roadmap
Sometimes a project, or the epics and issues it contains, can prevent you from accessing the roadmap.
Project exceeds issue or epic limit
If your project contains more than 3000 issues or 300 epics, the roadmap won’t display.
There’s a filter built into the roadmap, and it automatically exclude epics, if:
The epic was moved to the Done status category more than a year ago.
The epic was moved to the Done status category, and it has a due date from more than a year ago.
It's good practice to set due dates on your epics, so you’re reminded to mark them as done or adjust the due date. You can find the Due date field within the issue view of the epic.
No epic issue type
If your project doesn't have an epic issue type, the Roadmap won't display. Note that the issue type must be a high-level issue type, so a regular issue type that happens to be called "Epic" still won't work. To fix this, you can navigate to the Roadmap to either create a new epic issue type, or select an existing issue type and designate it as the epic issue type.
No date fields on epic issue type
Epic issue types must have a Start date and Due date field to display on the Roadmap. If these are deleted, you can navigate to the Roadmap to have them re-added.
Accidentally converted a story-level issue type to an epic
If you've mistakenly converted an issue type to an epic, and your issues no longer display on the board and backlog, you can restore these issues to their original state with the following steps:
Create a new story-level issue type.
Delete the 'wrong' epic type (that was converted).
As part of the issue type deletion process, you'll be asked which new issue type you'd like to move all your issues to.
Select the new issue type you created.
Rename this new issue type to your old one, if you want to.
Manage corrupt issues
An issue's considered corrupt if certain details, like the issue type, status, status category, or rank settings are invalid. The details might have been missing when the issue was created or something might have gone wrong with a bulk import.
The roadmap won’t display until the details in the corrupt issue are fixed.
To fix a corrupt issue, you must raise a support ticket. Our team will help fix the issue so you can continue using your roadmap.
Was this helpful?