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.
Customize your view on the roadmap
For a roadmap to be most effective, it should display the work that’s most relevant to you. What’s relevant often differs between roles, so you can customize your view to suit your needs.
Filter by status category: Choose to only view epics and issues in a specific status category, either To do, In progress, or Done.
View settings: A collection of settings that allow you to adjust your personal view of the roadmap. The settings only apply to you and although we remember your preference, you can change your view at any time.
Epic display options: Use the dropdown to select which epics to display. The current options are: All, Incomplete, or Complete.
Dependencies and progress: Add or remove dependencies and progress from your view.
Timeline: Toggle to a specific timeframe, on the fly. Divide by weeks, months, or quarters.
The roadmap already has some built-in filters to help with issue management and make things run faster. For now, your roadmap will only display 300 epics and 3000 issues. The roadmap also excludes any issues that are considered complete.
Completed issues in Jira Software
Admins in Jira Software might be familiar with an issue’s Resolution field. This field is set when an issue is moved from the In progress to Done status. It’s then that Jira Software considers the issue complete.
This behavior is automatically configured as part of default workflows. However, if a custom workflow is used, the behavior needs to be manually configured as a post function.
The roadmap relies on a different field — the Status category change date — to define completed issues. By referring to this field, the roadmap ensures a consistent approach between default and custom workflows. Learn more about Jira Software’s Resolution field and configuring post functions.
So, this means the roadmap doesn’t include:
Issues that were marked as Done over a year ago.
Issues that were resolved with a due date from over a year ago.
This logic will always apply to the roadmap, even if you adjust your view settings.
Adjust your view settings
The View settings will let you specify which epics to display, with the exclusions applied. You can refine your view so the roadmap displays All, Complete, or Incomplete epics.
Incomplete epics, even those created more than a year ago, will always be available on your roadmap.
To include dependencies and progress in on your roadmap, tick the checkbox. To exclude them, just untick the box.
The refined roadmap will automatically refresh to display your selections.
Apply filters on top of your custom view
To really focus your view on the roadmap, try adding filters.
You can display epics and issues in a certain status category, or particular issue types. Just keep in mind how your view settings and filters work together. For example, a roadmap won’t be able to display issues with the Done status category, if your view settings are set to display Incomplete epics.
Was this helpful?