Viewing work

このページの内容

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

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.

1 Select the hierarchy levels from which and to which you want to view issues.
2 Click 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.

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 work for more details.

5

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

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 or team.

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 work 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.

Filtering work

It can be easy to lose focus when you're planning work across multiple projects, releases, teams, and more. By filtering the work that's displaying in your plan, you can focus your attention on a specific scope of your plan, as needed.


Sample plan, with the teams filter applied

The following filters are available to use:

リリース Choose the relevant releases from the releases included in the plan. Note that when you filter the issues in your plan using releases, the release icons in your plan will also be filtered.
チーム Choose the relevant teams from the teams existing in the plan.
プロジェクト Choose the relevant projects from the projects being used as issue sources in the plan.
Labels Choose the relevant labels from the labels being used by the issues in the plan.
Dependencies

Choose which issues with dependencies to display, using any of the following:
  • All issues, to show all issues included in the plan, regardless of whether or not the issues have dependencies.
  • Has dependencies, to show only issues that have dependencies.
  • Specific issue, to show a specific issue from all the issues in the plan. The filtered issue will be displayed, whether or not it has dependencies. This helps you view any dependencies of that issue, or add a dependency to the filtered issue, if needed.

As an option, you can choose to include the dependency chain of a specific issue. This effectively filters both the direct dependencies and indirect dependencies of the issue.

For example, in your plan, you have TIS-1 blocking TIS-2 — with TIS-2 also blocking TIS-6 and PERF-1.

If you specifically filter for TIS-1, and you include its dependency chain, then the direct dependency TIS-2, and the indirect dependencies TIS-6 and PERF-1 will display in the plan.

See Managing dependencies to know more about dependencies.

課題の詳細 Filter issues by entering either the issue key or issue summary.


To filter issues in a plan:

  1. In your plan, click the Filters drop-down.
  2. Select which values to apply, for any of the available filters.
  • Click Clear all filters to quickly remove all filters and view all issues in your plan.
  • You can also use multiple filters, to further narrow down on the work you're trying to focus on. For example, you can filter for only the issues that have dependencies, and that are assigned to v3.0 release.

    Note that there may be times when some issues won't be returned, because of the multiple filters that have been applied. To continue with the example above, let's say TIS-67 has dependencies, and is assigned to v2.0 release. Even if the issue TIS-67 has dependencies, the issue might not be returned because it is not assigned to v3.0 release.

Displaying issue details

You can choose the issue details that you want to display in your plan. These details may include:

To display the relevant issue details in a plan, do any of the following, as needed:

Adding a field

To display issue details in a plan, you'll first need to add the relevant fields to the plan. These fields will be displayed as columns, and each field will contain the corresponding issue detail.

In the fields section of the plan, click more () > select the checkbox of the field you want to add.

Set a value for a field Click the cell of the relevant field, then specify the corresponding value for it.
Removing a field

In the fields section of the plan, click more () > clear the checkbox of the field you want to remove from the plan.

Reordering fields

The order of the columns in the fields section depends on the order that you add the fields to the plan. We're currently iterating on the best way to reorder fields for future versions.

  1. In the fields section of the plan, click more () > clear the checkboxes of all the fields.
  2. Select the checkboxes of the fields in the order in which you want the corresponding columns to display.

Customizing view settings

You can customize the view settings of your plan, to make it easier for your audience to consume the data in your plan. By customizing the view settings, you can make your timeline display the right information for you and your audience.

Sample plan, with issues grouped by assignee

Sample plan, with issues colored by status

To customize the view settings of a plan:

  1. In your plan, click the View settings drop-down.
  2. Select which settings to use, for any of the following options:
    • Group by, to group issues into separate swimlanes by assignee, project, or team.
    • Color by, to color issues by status or team.

Note that after customizing the view settings, you can still interact with the issues in the plan, e.g. dragging and dropping issues, or assigning issues to teams.

You can also use the group by and color by settings at the same time. For instance, you can group issues by project, and color issues by status, just like the sample plan below.

最終更新日: 2018 年 12 月 14 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.