プラン環境をセットアップする

はじめる前に

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.

To help you set your teams up for success, we've prepared this getting started guide that discusses how to set up Portfolio for Jira with your existing Jira instance.

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 つまたは複数のプロジェクトの課題が表示され、作業中の課題を柔軟に表示、管理およびレポートできます。Jira Software には 2 種類のボードがあります。

  • Scrum board — for teams that plan their work in sprintsMore about Scrum
  • Kanban board — for teams that focus on managing and constraining their work-in-progress. More about Kanban
プロジェクト

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.

Out of the three (3) issue sources, we recommend that you use Scrum boards. This gives you the ability to manage sprints from those boards, plan the capacity of future sprints, and assign issues to sprints — all directly from your Portfolio plan.

課題タイプと階層レベルの作成

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:

  1. 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 Jira


  2. When 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
    (info) 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.

  3. 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

When enabling the improved interface for the first time, you may not see any issues scheduled in the timeline section immediately. This can be due to several factors:

#1 The issues may have been calculated using the scheduler in Portfolio for Jira

この場合、課題には引き続きスケジュールされた日付がありますが、ターゲット日はありません。ターゲット日は改善されたインターフェイスで既定で使用されているため、タイムライン セクションでは課題が日付を含まないように見えます。

ただし、スケジュールされた日付を改善されたインターフェイスにコピーすることもできます。これを行うには、次の手順を実行する必要があります。

  1. プランのインターフェイスを無効化します。プランの設定ページから、[プランニング インターフェイス] > [改善されたインターフェイスを無効にする。] をクリックします。
  2. 以前のプラン レイアウトの [範囲] セクションで、左上にある上端のチェックボックスを選択し、プラン内のすべての課題を選択します。
  3. "ターゲットの設定" から、[計算したターゲット日を設定する] を選択します。
  4. プランで改善されたインターフェイスを無効化します。プランの設定ページから、[プランニング インターフェイス] > [改善されたインターフェイスを有効にする。] をクリックします。

#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

The teams field is actually a custom field in Jira. To make this field appear in Jira issues, you'll first need to add this custom field to the screen that's being used in the corresponding Jira project.

これを行うには、次のようにします。

  1. In Jira, click  > Issues.
  2. Click Custom fields.
  3. フィールドの一覧で [チーム] フィールドを探します
  4. [チーム] フィールドの > [画面] をクリックします。
  5. チーム フィールドを追加したい画面を選択します。
  6. [更新] をクリックします。

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

What are known as releases in Portfolio for Jira are known and treated as fix versions in Jira.

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:

  1. In Jira, click  > Issues.
  2. Select Fields > Field Configurations to open the View Field Configurations page, which lists all your field configurations.
  3. 対象のフィールド設定を見つけ、[設定] リンクをクリックします。
  4. [修正対象バージョン] フィールドを見つけます。
  5. 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.

Enabling the improved interface in a plan

As long as you're running Portfolio for Jira (version 3.0 and later), any newly created plans will have the improved interface enabled by default.

However, for plans that have already existed before upgrading to version 3.0 or later, you'll need to enable the interface in your individual plans. Your plan will not get the new interface until this is enabled in the plan itself.

Other things to note:

  • You must be using the latest version of Portfolio for Jira.
  • We highly recommend you use Chrome or Firefox as your browser. You can also use Internet Explorer 11 and Safari — we've fixed some issues specific to these browsers in the latest version.
  • We're simplifying the experience of scheduling issues by using only one type of date by default — target dates. You can still use other custom date fields that you may have already configured. However, you'll first need to add these custom fields to your plan before enabling the improved interface.

To enable the improved interface:

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click more () > Try the improved interface. The planning interface page will be displayed.
  3. Click Enable improved interface to switch on the new interface for your plan.
  • 新しく作成されたプランや、改善されたインターフェイスが初めて有効化された既存のプランの場合、デフォルトで以下が行われます。
    • プランには、2 つ以上の課題を持つ最高の階層レベルから課題が表示されます。プランの最高のイニシアチブ レベルに 2 つ以上の課題がある場合、イニシアチブから課題が表示されます。
    • プランで、エピックよりも上の任意のレベルに課題が 1 つしかない場合、課題はエピック レベルから表示されます。
    • The target start date, target end date, and status columns will be displayed in the fields section.
    • 課題は、すべての課題で最も早い開始日、元も早いリリース、最も遅い終了日、および最も遅いリリースに基づき、タイムラインの幅に合わせて表示されます。
    • これらの詳細や変更はいつでも変更できます。詳細は、「課題の詳細の表示」を参照してください。
  • To stop using the new interface in a plan, from the plan configuration page, click Planning interface > Disable improved interface.

最終更新日 2019 年 11 月 27 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.