Filtering issues



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


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

Sample plan with the teams filter applied

The following filters are available to use:


Filter issues by entering either the issue key or issue summary.

You can also enter multiple issue keys and issue summaries, to filter for multiple issues faster. Use a comma or semicolon to separate the issue keys and issue summaries.


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.

To quickly filter for issues that don't have any releases, choose No release.

チームChoose the relevant teams from the teams existing in the plan. To quickly filter for issues that are not assigned to any teams, choose No team.

Choose the relevant assignees to filter for issues that are assigned to these users. The available users can come from either the users that belong to the teams in the plan, or from users who may be assigned to any issue in the plan.

To quickly filter for issues that are not assigned to any teams, choose Unassigned.


Choose the relevant sprints from the board issue sources existing in the plan. The sprints are grouped together by teams.

You can also quickly filter for issues that are assigned to all completed sprints, or all active sprints, or all future sprints, or no sprint at all.


Choose the relevant projects from the project issue sources in the plan.

Note that only the releases related to the filtered projects will be displayed in the timeline, letting you focus on only the relevant project releases.

課題タイプChoose the relevant issue types from the issue types available in the plan.
コンポーネントChoose the relevant components from the components being used by the issues in the plan.
ラベルChoose the relevant labels from the labels being used by the issues in the plan. To quickly filter for issues that don't have any labels, choose No label.

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.

As an alternative, if you're viewing the dependencies of an issue from its dependency badge, click the filter by dependencies link for the issue. The corresponding dependent issues will be displayed in the roadmap view.

See Managing dependencies to know more about dependencies.


Choose the relevant statuses of the issues that you want to see in the plan.

You can also filter for issues that are not saved in Jira just yet under the To do status category.

警告Choose to display only the issues that have warnings in the plan. Hover over the warning icons beside the filtered issues to know what the warnings are for, and how to fix these accordingly.
Show full hierarchy

As an optional setting, choose to display the full hierarchy of issues, no matter the other filters that you've set up.

If you're filtering for issues with the In progress status, and you do not show the full hierarchy, only issues with the filtered status will be displayed, as shown below:

Using the same status filter, if you choose to show the full hierarchy, all child issues of the parent issue that matches the filter will also be displayed. The child issues that do not match the status filter will be slightly grayed out in appearance, as shown below:

Filtering issues

When you're filtering issues, some issues that do not match the applied filters may still display in your plan. For example, if you're filtering for issues in the iOS App project, the following will happen, as shown in the sample plan below:

  • iOS issues will be displayed in solid colored rows, and
  • issues of other projects (PM issues, in the sample plan) will be displayed in greyed out rows.

To filter issues in a plan:

  1. In your plan, click the Filters drop-down.
  2. Select which options to apply, for any of the available filters.
  • When filtering issues, all the parent issues up to the corresponding highest hierarchy level, and all the child issues down to the corresponding lowest hierarchy level will be displayed. What will not be displayed are the sibling issues, if these issues do not match the filters that have been set.
  • To quickly remove all filters and view all issues in your plan, click Clear all filters.

Using multiple filters

You can use use multiple filters, to further narrow down on the work you're trying to focus on.

For example, if you're filtering for only the issues that have dependencies, you may see your plan displaying something like this:

To further narrow down on the results, let's say you're filtering for the issues that are assigned to release 1.2. Your plan will then display the following:

The filtered results indicate the following:

  • Even if TIS-140, TIS-132, and TIS-133 have dependencies, these issues are not displaying because these are not assigned to release 1.2.
  • Being the parent issues higher up in the hierarchy, TIS-116 and TIS-4 are indirect results of the filters applied. These issues are then displaying, and are slightly grayed out.
最終更新日 2020 年 1 月 6 日


Powered by Confluence and Scroll Viewport.