If you're using the improved planning interface (3.0 and later), this page is for you. If you're using live plans (2.0 to 2.27), head to Portfolio for Jira live plans.
When planning work, you're likely to be managing multiple issues that span multiple projects. It's easy to lose track of your work at one point or another, when you're across multiple work streams.
The roadmap view of your plan lets you see all the work that's relevant to you. The improved interface lets you use the different elements in this view, so you can focus on only the relevant details. For example, you can deep-dive into the details by narrowing down the available filters, or go wider by expanding the timeframe or hierarchy levels.
|1||Select the hierarchy levels from which and to which you want to view issues.|
Click to expand an issue to view its child issues.
You can also quickly expand or collapse the issues in the hierarchy.
In doing so, the issues will be expanded according to the hierarchy levels that have been set. In the example above, the hierarchy levels are set from initiative to story. This means that all issues from the initiative level down to the story level will be expanded.
Any issues that have been marked as done in Jira, that don't have a resolution set, will not be included in the plan.
At the bottom of the scope section, you'll find the issues without parent section, which displays the issues that do not belong to any parent issue when expanded.
This section also displays the issues according to their hierarchy levels. Expand a hierarchy level to view the issues of that hierarchy level.
Use filters to display the relevant issues in your plan, like projects, releases, teams, issue details, and more. See Filtering issues for more details.
Choose the issue details that you want to display in your plan, which include:
See Displaying issue details to learn more.
Above the timeline section, choose the timeframe settings as needed:
Notes when configuring timeframe settings
You may have issues with dates that go beyond the selected timeframe. For such issues, you'll see an arrow at the end of the schedule bar — this arrow indicates that the date goes beyond the timeline.
In the example below, the timeframe is set to 1 year, and you have an issue has a start date of 07 Jan 19, which goes beyond the timeline.
By clicking the arrow of the schedule bar, the timeframe jumps to the start date of the issue, while the timeframe automatically sets itself into the corresponding custom date range.
Customize the view of the timeline, to make it easier for your audience to consume your plan. The following view settings are available:
See Customizing view settings to know more.
The schedule bar, which represents the schedule duration of an issue in a plan, based on the dates that have been set for the issue.
Ideally, an issue would have both start and end dates, but it's quite possible for an issue to have just one of the dates. In this case, the schedule bar displays in a solid color on the end of the date that's been set. The solid color gradually fades towards the other end of the schedule bar, where the date hasn't been set.
For newly created plans and existing plans where the improved interface is enabled for the first time, the following will take place by default:
- The plan will display issues starting from the highest hierarchy level that has at least 2 issues. If the plan has at least 2 issues at the highest initiative level, then it will display issues starting with initiatives.
- If the plan has only 1 issue at any level above epics, then the issues will be displayed starting at the epic level.
- The target start date, target end date, and status columns will be displayed in the fields section.
- The issues are displayed to fit the width of the timeline, based on the earliest start date, earliest release, latest end date, and latest release of all issues in the plan.
- You can change these details and settings any time moving forward. See Displaying issue details for more information.