作業を表示する
作業を計画する際には、複数のプロジェクトを横断する複数の課題を管理する可能性があります。複数の作業ストリームを横断していると、作業を見失いやすくなります。
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 | 課題を表示する際の階層レベルの範囲を選択します。 |
| 2 | クリックして課題を展開し、子課題を表示します。 |
| 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. また、このセクションには、階層レベルに従った課題が表示されます。階層レベルを展開すると、その階層レベルの課題が表示されます。 |
| 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 | プランに表示する課題の詳細を選択します。これには次が含まれます。
詳細は、「課題の詳細の表示」を参照してください。 |
| 6 | Above the timeline section, choose the timeframe settings as needed:
タイムフレーム設定を構成する際の注意事項
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 | ユーザーがプランを見やすいよう、タイムラインのビューをカスタマイズします。次の表示設定を利用できます。
詳細については「表示設定のカスタマイズ」を参照してください。 |
8 | プランでリリースの詳細を確認します。これは、リリースが逸脱していないかどうかの監視に役立ちます。
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
次のフィルターを使用できます。
| Releases | 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. |
| ラベル | Choose the relevant labels from the labels being used by the issues in the plan. |
| 依存関係 | 次のいずれかを使用して、依存関係を持つどの課題を表示するかを選択します。
オプションとして、特定の課題の依存関係チェーンを含めるよう選択できます。これは、課題の直接的な依存関係と間接的な依存関係の両方をフィルタリングします。 たとえば、プラン内で TIS-1 が TIS-2 をブロックし、TIS-2 も TIS-6 と PERF-1 をブロックするとします。 TIS-1 でフィルタリングして、依存関係チェーンを含めると、直接の依存関係 TIS-2 と、間接的な依存関係 TIS-6 および PERF-1 がプランに表示されます。 依存関係の詳細については、「依存関係の管理」を参照してください。 |
| 課題の詳細 | Filter issues by entering either the issue key or issue summary. |
プランで課題をフィルタリングする方法
- プランで、[フィルター] ドロップダウンをクリックします。
- 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.
課題の詳細の表示
プランに表示する課題の詳細を選択できます。これらの詳細は次の場合があります。
- Issue details that Portfolio for Jira accesses from Jira, like assignees, issue statuses, sprints, releases, dependencies, and more.
- any custom fields existing in Portfolio, like target start dates, target end dates, and teams.
- any custom fields configured in Jira, as long as it is a single-line text field. Note that the custom field must already be added in Portfolio before enabling the new experience.
At the moment, there's no way to add custom fields in the new experience. All necessary custom fields must be added to a Portfolio plan before the new experience is enabled in the plan. As a workaround, you can disable the new experience for the plan, add the relevant custom fields, and the reenable the new experience.
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 ( |
| 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 ( |
| 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.
|
表示設定のカスタマイズ
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:
- プランで、[設定を表示] ドロップダウンをクリックします。
- 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.
