It can be easy to lose focus when you're planning work across multiple projects, releases, teams, and more. By filtering the issues that are displaying in your plan, you can focus your attention on a specific scope of your plan.
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.|
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 projects from the projects being used as issue sources 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:
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.
|ステータス||Choose the relevant statuses of the issues that you want to see in the plan.|
|警告||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:
When you're filtering issues, some issues that do not directly match the applied filters may still display in your plan. This means that 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.
For example, if you're filtering for issues in the TIS project, and there are TIS issues that have child issues coming from the PERF project, then the following will happen, as shown in the sample plan below:
- TIS issues will be displayed in a solid color, and
- PERF issues (which are children of TIS issues) will be displayed in a lighter shade.
To filter issues in a plan:
- In your plan, click the Filters drop-down.
- Select which values to apply, for any of the available filters.
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.