Viewing work

Still need help?

The Atlassian Community is here for you.

Ask the community

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. With the new experience, you can 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.

1Select the hierarchy levels from which and to which you want to view issues.
2Click to expand an issue to view its child issues.
3

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.

4

Use filters to display the relevant issues in your plan, like projects, releases, teams, issue details, and more. See Filtering issues for more details.

5

Choose the issue details that you want to display in your plan, which include:

  • issue details that Portfolio accesses from Jira, which may include assignees, issue statuses, sprints, releases, dependencies, and more
  • any custom fields existing in Portfolio, like target start datestarget end dates, and teams
  • any custom fields configured in Jira, like single-line text fields and single-choice select fields

See Displaying issue details to learn more.

6

Above the timeline section, choose the timeframe settings as needed:

  • 3M: for issues scheduled for the next 3 months, starting from the current day
  • 1Y: for issues scheduled for 1 year, starting from the current day
  • Fit: for issues scheduled from the earliest start date and latest end date in the plan itself, with the issues displayed to fit the width of the timeline
  • Custom: for issues scheduled within a particular date range

Notes when configuring timeframe settings

You may have issues with target start dates or target end dates that go beyond the selected timeframe. For such issues, you'll see an arrow at the end of the schedule block — this arrow indicates that the target date goes beyond the timeline.

In the example below, the selected timeframe is 1 year (1Y), and the highlighted issue has a start date of 26 Jul 18, which goes beyond the timeline.

By clicking the arrow of the schedule block, the timeframe updates into a custom date range, as shown below.

7

Customize the view of the timeline, to make it easier for your audience to consume your plan. The following view settings are available:

  • Group by: Group issues into separate swimlanes by assignee, project, or team.
  • Color by: Color issues by status, team, or label, or by the corresponding values of any single-choice select and multiple-choice select custom fields being used in the plan.

See Customizing view settings to know more.

8

View the details of a release in your plan. This is helpful in monitoring if any releases are off track.

Note that when you filter the issues in your plan using releases, the release icons in your plan will also be filtered. See Filtering issues for more details.

9

The schedule block, which represents the schedule duration of an issue in a plan, based on the target dates that have been set for the issue.

Ideally, an issue would have both target start and target end dates, but it's quite possible for an issue to have just one of the dates. In this case, the schedule block displays in a solid color on the end of the target date that's been set. The solid color gradually fades towards the other end of the schedule block, where the target date hasn't been set.

Last modified on Feb 25, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.