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.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
This page refers to the roadmap view in Jira Software and not Advanced Roadmaps, the cross-project planning tool only available as part of Jira Software Cloud Premium and Enterprise.
Unless otherwise noted, the roadmap view in Jira Software is the same for both company-managed and team-managed projects.
Give your project context by showing issues up to one year old, or show no completed issues to live in the moment. By default, your roadmap shows issues that have been completed within the last 12 months.
To change how many completed issues show on your roadmap:
From your roadmap, navigate to the View settings menu at the top-right of your view.
Under the heading Issue display range, select the timeframe you’d like to show on your roadmap from the dropdown.
To show no past issues on your roadmap, select Hide all completed epic issues.
Your roadmap will update automatically.
How Jira Software defines completed issues in the roadmap view
Jira Software looks at two different fields to evaluate whether an issue is done:
In company-managed projects, it looks at the issue’s Resolution field, set via a post function when an issue is moved from an In progress to Done status. Learn more about Jira Software’s Resolution field and configuring post functions.
In team-managed projects, it looks at the category of the issue’s status. Issues are considered resolved when they’re moved from an In progress to Done status category.
The roadmap refers to the Status category change date to define completed issues. This makes sure the roadmap always refers to a consistent field and is consistent across multiple workflows.
Was this helpful?