This information applies to Portfolio for Jira 3.0 and later. If you're using an earlier version (2.0 to 2.27) see the Portfolio for Jira live plans documentation.
This article provides a high-level introduction to the Roadmap section of a plan. If you're just getting started with Portfolio, this guide will help you understand what you're looking at. We’ll also touch on some of the ways that you can customize how plan data is displayed to best suit you, your team, and your stakeholders.
Pictured below is a sample Portfolio plan. Following that are explanations of the features and sections called out by number.
1) Hierarchy settings
Use the Hierarchy dropdown menus to select the highest-to-lowest hierarchy level that you want to view issues for. For example, Initiative to Sub-task, or Epic to Story.
2) Issues: expand and collapse
When there’s an arrow (>) in front of an issue it indicates that there are child issues. Click the arrow to expand the collapsed rows and and view the child issues.
You can also click the Issue dropdown menu to expand or collapse all issue hierarchies in the plan:
If you select Expand all and the hierarchy levels are set from initiative to story, as pictured above, you’ll only see issues within that range. To see issues from a higher or lower level, change the Hierarchy setting.
Sometimes a plan can include issues that don’t have a parent issue. For example, a story that doesn’t belong to an epic. Orphaned issues are grouped in the scope section and labeled x issues without parent. Click the arrow (>) to expand the row and view them.
Use the Filters menu to display issues relevant to what you’re focused on. For example, you can filter by project or team to forecast upcoming work, or filter by assignees to delegate work. You can also filter by issue details, issue types, dependencies, and more.
The columns in the fields section display issue details that Portfolio accesses from Jira. This includes sprints, assignees, releases, dependencies, priorities, and more. By default, newly created plans include columns for the following fields:
- Target start
- Target end
Click the more (…) menu to add or remove issue details. You can also click on a column to collapse or expand it, and change the order that they’re displayed in.
6) Timeframe settings
The timeline, far right, is the visual indicator of your roadmap. Above the timeline are settings for the timeframe to display:
- 3M — Updates the timeline to show the next 3 months, starting from the current day.
- 1Y — Updates the timeline to show the next year, starting from the current day.
- Fit — タイムラインの期間を調整して、すべてのスケジュール バーの始点と終点が表示されるように合わせます。
- Custom — 次の 2 つのオプションから選択できます。
- Fixed — Set a specific start and end date to view that time range on the timeline.
- Relative — Select a period of time that is relative to the current date. For example, show the past 2 weeks and the next 3 months. The timeline view will update daily based on the time range specified.
The colored bars pictured in the sample plan up top are schedule bars. If you don’t see any in your plan, it’s because there are no dates set for your issues yet.
Use View settings to customize how issues and related information is displayed, categorized and colored in the roadmap view of your plan. For example, you can group issues by swimlanes and choose to have them grouped by project, team or sprint. You can also choose the sort order for issues in the plan, show or hide issue warnings, and more.
8) Release details
There’s a Releases section in your plan that we won’t explore here, however it’s useful to know that release progress can be tracked from the timeline, and release details are easily accessible, too.
9) Schedule bars
“Schedule bars” are the colored bars on the timeline associated with issues that have dates. If there is no start or end date scheduled for an issue, you can click in the timeline section of the issue’s row to add a schedule bar: