Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your existing Jira Software Cloud site 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 next-gen projects.
Create powerful rules to start automating your manual, repetitive processes.
Troubleshoot the roadmap
Are you on the right help page?
The following information only applies to classic projects.
To check which project you need help with, look at the bottom of your project’s left-hand sidebar:
If you see an icon stating You’re in a next-gen project with Give feedback and Learn more menu items, you're in a next-gen project. Check out our next-gen project documentation.
If you don’t, you're in a classic project.
Sometimes a project, or the epics and issues it contains, can prevent you from accessing the roadmap.
Board filter exceeds issue or epic limit
The roadmap displays all issues and epics in your board filter. If your board filter contains more than 3000 issues or 300 epics, the roadmap won’t display.
To help clear the clutter there’s also a filter built into the roadmap, and it automatically excludes epics if they meet these specific criteria:
The epic is Marked as done in Backlog > EPICS on the left side of the board.
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 in the epic issue view. If it's not visible, an admin might need to configure your issue detail view.
A board admin can also adjust the board filter to only display recent work.
To only display issues created within the last year:
Go to Projects then select the relevant project.
Select Issues and filters > Advanced search.
In the search bar, enter this query, but replace NAME with the name of your project. Adjust the dates to match the current year:
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.
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, add a new epic issue type, or select an existing issue type and designate it as the epic issue type. Learn more about issue types.
Epics don’t display on the roadmap when using a Kanban board
The roadmap is based on the same JQL filters as your board. If you’re using a Kanban board, it’s likely that your board will have a JQL filter that prevents epics from displaying on the board. The query could look like this:
project = FOO and issueType != Epic ORDER BY Rank
To display epics on your roadmap, your board admin can remove the JQL query from the board filter, and add it to the Kanban board sub-filter instead.
To adjust your JQL filter:
If you’re not already there, navigate to your classic project.
From your board, go to More (···) > Board settings.
In the General tab of your board settings, find Filter > Saved filter. Select Edit filter query.
From your Filters settings, remove (or cut) this clause: issueType != Epic. Run the search, then save your changes.
Return to the General tab of your board settings. Find Filter > Kanban board sub-filter.
Edit the query by hovering over the text. Paste the and issueType != Epic clause into the field.
Select Update to save your changes.
Accidentally converted a story-level issue type to an epic
If you've converted another 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:
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.
Was this helpful?