2. Preparing your planning environment
はじめる前に
Depending on how your organization is structured, the content on this page is meant for Portfolio for Jiraadministrators or Portfolio plan owners, and the project administrators of the Jira projects that you want to include in your plans.
The guide discusses the typical end-to-end path that users and administrators may find themselves taking part in when using Portfolio for Jira. You'll also find high-level content on Portfolio concepts, as well as some recommendations and optional steps you can consider, as you flesh out your plan.
プラン環境を準備する
Now that you've installed Portfolio for Jira in your Jira instance, you can start thinking about how best to set up your plans. You need to do this to ensure that you're efficiently planning work for your teams.
Here are some concepts that will come in handy, when preparing your planning environment:
課題ソースを使用する
A plan in Portfolio for Jira provides an aggregated view of all the issues that your teams are handling in Jira. With your plan consuming issues coming from Jira, you can then proceed to create a schedule for your teams to work with.
For Portfolio for Jira to capture the latest and greatest data from Jira, you'll need to organize your work in Jira, into what we call issue sources in Portfolio:
| ボード | 1 つのボードに 1 つ以上のプロジェクトの課題が表示され、作業中の課題を柔軟に表示、管理、報告することができます。Jira Software には 2 種類のボードがあります。
|
| プロジェクト | A project in Jira is a collection of issues that is defined according to your organization's requirements. For example, it could be a software development project, a marketing campaign, or a website enhancement request system. |
| フィルター | Your board's filter is a Jira issue filter (a JQL query) that specifies which issues are included on your board. For example, your board may include issues from multiple projects, or from only one project, or from a particular component of a project. Only the administrator of a board or a user with the Portfolio for Jira administrator global permission can configure a board's filter. |
課題タイプと階層レベルの作成
By default, the issue types that are available in a newly created Portfolio plan will be the issue types that have been defined for the Jira projects that are included in the plan. Over time, you can create more issue types on those Jira projects, and these new issue types will also be available for use in your plan.
Portfolio for Jira comes with this default hierarchy level setup:
Epic, which maps to the epic issue type
Story, which maps to all other standard issue types. With the default Jira issue types, this means that stories, bugs, and tasks map to the story hierarchy level.
Sub-task, which maps to all sub-task issue types — essentially sub-tasks, of the default Jira issue types
When planning work across multiple projects and teams, you may need to create levels that are higher than the epic hierarchy level. A common example that's largely used in the industry is the initiative hierarchy level. To get this hierarchy level in your plan, you need to:
In Jira, create the initiative issue type, if it's not created yet.
To complete this step, you must be logged in as a user with the Jira administrators global permission .
Creating the initiative issue type in JiraWhen the initiative issue type is already created, add the issue type to one of the projects that you're including in your plan.
To complete this step, you must be logged in as a user with the Jira administrators global permission.
Adding the initiative issue type to a Jira project
Alternatively, you can consider creating a dedicated Jira project, and then create all the initiatives you need in that project. You can then link the epics across all your projects to the initiatives in that dedicated project for initiatives.In Portfolio for Jira administration, add the initiative hierarchy level in Portfolio. Make sure to map the initiative issue type to the hierarchy level.
Adding the initiative hierarchy level, and mapping the initiative issue type to the hierarchy level
See Creating an issue type (Administering Jira Software Server documentation) and Configuring initiatives and other hierarchy levels to learn more.
依存関係を定義する
You can configure Portfolio for Jira to use the issue links that are set up in Jira, so that you can define scheduling dependencies. When adding issue links, you need to define the relationship between the issues to suit how your team works.
Note that any changes you make to issue dependencies in Portfolio for Jira will apply to all existing Portfolio plans.
Check out Managing Portfolio dependencies to know how to define dependencies in your plan.
Migrating date fields to Portfolio
#1 The issues may have been calculated using the scheduler in Portfolio for Jira
この場合、課題には引き続きスケジュールされた日付がありますが、ターゲット日はありません。ターゲット日は改善されたインターフェイスで既定で使用されているため、タイムライン セクションでは課題が日付を含まないように見えます。
ただし、スケジュールされた日付を改善されたインターフェイスにコピーすることもできます。これを行うには、次の手順を実行する必要があります。
- プランのインターフェイスを無効化します。プランの設定ページから、[プランニング インターフェイス] > [改善されたインターフェイスを無効にする。] をクリックします。
- 以前のプラン レイアウトの [範囲] セクションで、左上にある上端のチェックボックスを選択し、プラン内のすべての課題を選択します。
- "ターゲットの設定" から、[計算したターゲット日を設定する] を選択します。
- プランで改善されたインターフェイスを無効化します。プランの設定ページから、[プランニング インターフェイス] > [改善されたインターフェイスを有効にする。] をクリックします。
#2 The issues may not have been calculated or scheduled, before the improved interface was enabled
この場合、プランでの課題のスケジュール設定を開始するには、「作業のスケジュール」を参照してください。
#3 課題はスケジュールされている可能性があるが、"親のない課題" セクションで非表示になっています
この場合、このセクションを展開してスケジュールされた課題を表示する必要があります。
Surfacing important details across Portfolio for Jira and Jira
Some Jira issue details are not displayed in Portfolio plans by default. Likewise, there are also issue details from Jira that are not readily displayed in Jira. Make sure to do the following, so that all the important issue details are readily available across both.
Making the teams field appear in Jira issues
これを行うには、次のようにします。
- In Jira, click
> Issues. - Click Custom fields.
- フィールドの一覧で [チーム] フィールドを探します
- [チーム] フィールドの
> [画面] をクリックします。 - チーム フィールドを追加したい画面を選択します。
- [更新] をクリックします。
Each time a team is assigned to an issue in your plan, and you save this change to Jira, the team field will appear in the corresponding issue in Jira.
Making fix versions appear in Jira issues
If the fix version field is hidden in your Jira issues, then the releases you set in your Portfolio plan will not display in the corresponding issues in Jira.
To display the fix version field in Jira:
- In Jira, click
> Issues. - Select Fields > Field Configurations to open the View Field Configurations page, which lists all your field configurations.
- 対象のフィールド設定を見つけ、[設定] リンクをクリックします。
- [修正対象バージョン] フィールドを見つけます。
- In the Operations column, click Show.
Each time a release ise set for an issue in your plan, and you save this change to Jira, the release will appear as the fix version for the corresponding issue in Jira.