作業の計画
Once your plan is up and running, you're just about ready to plan more work for your teams. Most likely, your plan will already have issues in it, based on the issue sources you've previously selected.
You may also need to create more issues, to accommodate high-level work as they come. In the new experience, we're making it more straightforward and intuitive for you to create issues directly in your plan.
Note that at any point in time during planning, you may just be planning high-level work — and that's fine. This essentially means that during high-level planning, it's typical to have placeholder estimates, and even skip specifying issue details, like assignees and target dates. Your teams can define more accurate values for these details later on.
Also, note that it's easy to lose focus when you're planning work across multiple projects, releases, teams, and other factors. We recommend you filter the work in your plans, so you can focus on a specific part of your work, as needed. See Viewing work for more details.
On this page:
課題の作成
Before creating issues, make sure that you've already done both tasks:
- created the initiative issue type in at least one of the projects that's being used in your plan
- configured the hierarchy levels of your plan, as needed
そうしないと、一部の課題タイプを使用できません。詳細については、「イニシアチブおよび他の階層レベルの構成」をご確認ください。
You can create issues directly in your plan without having to jump back to Jira, and there are several ways to do this in the new experience:
Also, note that the default duration for issues would depend on the timeframe in which you're viewing the plan. You can always edit the duration after the issue is created.
- 3M: 1 週間
- 1Y: 1 か月
- Fit: The default duration depends on the date range of the issues in the timeline, which affects the width of the issues in the timeline. If the width fit is small, then the default duration could perhaps be a week or a month.
- Custom: The default duration depends on the duration that you set between the start and end dates. If you set a short period of time, then the default duration would be shorter as well.
ある課題の子課題を作成する
A plan typically contains issues coming from multiple issue sources, such as boards, projects, or filters. As a best practice, it would help you plan work and create issues more efficiently if you keep in mind the issue source, and the parent issue of the issue you're creating. This helps you create child issues of issues across multiple issue sources, where it makes most sense.
ある課題の子課題を作成する
特定の課題の子課題を作成するには:
- プランの [スコープ] セクションで、作成する課題の [親課題] に移動します。
- Hover on the parent issue > click + > select the hierarchy level for the issue you're creating. This will add a row for the new issue, right below the parent issue.
- In the new row, select the issue type for the new issue > select the corresponding project.
- Give the new issue a name, then click Enter.
- If already known, specify other issue details, like assignee, team, estimate, sprint, release, and target dates.
プランのロードマップ ビューで、タイムライン セクションの上にある [変更を確認] をクリックします。[変更を確認] ダイアログが表示され、既定ですべての変更が選択されます。
While reviewing your changes, perform the following as needed:
- To view multiple changes, expand the corresponding item in the 'What changed' column.
- With all the checkboxes already selected by default, clear the ones for the changes you do not want to save in Jira. While these changes won't be saved in Jira, these will still exist in your Portfolio plan.
- Select the checkboxes of the changes you want to save in Jira, then click Save selected changes in Jira.
- To discard any changes, select the checkboxes of these changes, then click Discard selected changes. These changes will then be discarded from your plan, and the values will revert to the ones currently saved in Jira.
同じ階層レベルで課題を作成する
兄弟課題、つまり同じ階層レベルの課題を作成することもできます。
同じ階層レベルで課題を作成する
同じ階層レベルで課題を作成するには:
- プランの [スコープ] セクションで、作成する兄弟課題と同じ階層レベルの課題を検索します。
- Hover on the issue > click + > select the same hierarchy level. This will add a row for the new issue, right below the issue you'd referenced.
- In the new row, select the corresponding project.
- Give the new issue a name, then click Enter.
- If already known, specify other issue details, like assignee, team, estimate, sprint, release, and target dates.
プランのロードマップ ビューで、タイムライン セクションの上にある [変更を確認] をクリックします。[変更を確認] ダイアログが表示され、既定ですべての変更が選択されます。
While reviewing your changes, perform the following as needed:
- To view multiple changes, expand the corresponding item in the 'What changed' column.
- With all the checkboxes already selected by default, clear the ones for the changes you do not want to save in Jira. While these changes won't be saved in Jira, these will still exist in your Portfolio plan.
- Select the checkboxes of the changes you want to save in Jira, then click Save selected changes in Jira.
- To discard any changes, select the checkboxes of these changes, then click Discard selected changes. These changes will then be discarded from your plan, and the values will revert to the ones currently saved in Jira.
任意の階層レベルで課題を作成する
大まかな作業を計画していて課題を手短に作成するだけの場合は、任意の階層レベルで課題を作成できます。これは、作成する課題がいくつかあるもののそれらを親課題に関連付けられない場合に役立ちます。
任意の階層レベルで課題を作成する
任意の階層レベルで課題を作成するには、次の手順に従います。
- プランの [スコープ] セクションで [+ Create issue (+ 課題の作成)] をクリックします。
- 課題の階層レベルを選択します。これにより、親課題のないその他の課題と同様に、[スコープ] セクションの下部に新しい課題が作成されます。
- Give the new issue a name, and click Enter.
- 必要に応じて、対応する課題の詳細を指定します。
- ストーリー レベルに複数の課題タイプがマップされている場合に必要な課題タイプ
- Issue source, for when your plan has multiple issue sources, i.e. boards, projects, and filters
- If already known, specify other issue details, like assignee, team, estimate, sprint, release, and target dates.
プランのロードマップ ビューで、タイムライン セクションの上にある [変更を確認] をクリックします。[変更を確認] ダイアログが表示され、既定ですべての変更が選択されます。
While reviewing your changes, perform the following as needed:
- To view multiple changes, expand the corresponding item in the 'What changed' column.
- With all the checkboxes already selected by default, clear the ones for the changes you do not want to save in Jira. While these changes won't be saved in Jira, these will still exist in your Portfolio plan.
- Select the checkboxes of the changes you want to save in Jira, then click Save selected changes in Jira.
- To discard any changes, select the checkboxes of these changes, then click Discard selected changes. These changes will then be discarded from your plan, and the values will revert to the ones currently saved in Jira.
Removing an issue from a plan
You can remove an issue from a plan via several methods, depending on whether you're using the current plans or the new planning experience.
Removing an issue in current plans
You can remove issues from a plan by doing one of the following methods:
| 1 | Removing issues from the plan directly from the scope table |
|
| 2 | Accessing the 'Create plan' wizard, and removing the issues from the scope of your plan | This only works for issues that have already been committed to Jira, which essentially means the issues already exist in your Jira instance.
|
| 3 | Reverting the issues you've just created in your plan, before committing these changes in Jira |
|
Removing an issue in the new planning experience
We're still iterating on how best to remove issues from plans in the new experience. At this time, you can remove issues doing one of the following methods:
| 1 | Discarding the issues you've just created in your plan, before saving these changes in Jira |
|
| 2 | Accessing the 'Create plan' wizard, and removing the issues from the scope of your plan | This only works for issues that have already been committed to Jira, which essentially means the issues already exist in your Jira instance.
|
シナリオを使用する
At the moment, for scenarios to work in the new experience, the corresponding scenarios should already be configured in the plan before the new experience is enabled in that plan.
In case you haven't configured scenarios just yet, you can disable the new experience, then configure scenarios in the previous layout, and then enable the new experience in the plan again.
In the new planning experience, you can use existing scenarios to see how specific changes across these different scenarios can affect your plan. This is a handy feature that can help you decide which scenarios is most realistic.
Once you've determined the most realistic scenario, you can then use this scenario to keep planning work for your teams, and then save whatever changes you've made in this scenario back to Jira.
Sample plan, with configured scenarios available
Linking an issue to a parent issue
課題を親課題にリンクするには、スコープ セクションで課題を親課題にドラッグ アンド ドロップします。課題は、プランで構成された対応する階層レベルの親課題にのみリンクできることに注意してください。つまり、エピックをストーリーの親課題として設定した場合、ストーリー課題はエピック課題にのみリンクできます。
課題を親課題にリンクする方法
- スコープ セクションで、親課題にリンクしたい課題を見つけます。
- 対応する階層レベルの親課題に、課題をドラッグ アンド ドロップします。
プランのロードマップ ビューで、タイムライン セクションの上にある [変更を確認] をクリックします。[変更を確認] ダイアログが表示され、既定ですべての変更が選択されます。
While reviewing your changes, perform the following as needed:
- To view multiple changes, expand the corresponding item in the 'What changed' column.
- With all the checkboxes already selected by default, clear the ones for the changes you do not want to save in Jira. While these changes won't be saved in Jira, these will still exist in your Portfolio plan.
- Select the checkboxes of the changes you want to save in Jira, then click Save selected changes in Jira.
- To discard any changes, select the checkboxes of these changes, then click Discard selected changes. These changes will then be discarded from your plan, and the values will revert to the ones currently saved in Jira.
課題を削除する
You cannot delete issues directly from a plan, if these issues have already been saved in Jira. You'll need to delete the issue from Jira, and to do this, you'll need the 'delete issue' project permission.
See Removing an issue from a plan to know how to delete issues that haven't been saved in Jira yet.