イニシアチブおよび他の階層レベルの構成

このページの内容

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

Portfolio for Jira lets you view your team's work in your Jira application with the big picture in mind, so that you can efficiently plan work that can span multiple projects and involve multiple teams. As such, it's important to understand the concepts of hierarchy levels and initiatives.

Portfolio for Jira essentially groups your work items in hierarchy levels, with the default hierarchy level being:

  • Epics – These are the products of higher-level priorities being broken down into smaller and more manageable chunks of work. Epics can span multiple sprints in a Jira project, and are comprised of multiple stories.
  • Stories – At the bottom of the hierarchy level are user stories, which typically capture functionality requirements. Stories are the units for work being done in Jira, and your team typically estimates the effort needed to complete these stories.
  • Sub-tasks – Sub-tasks are smaller chunks of work that need to be completed, to complete a story. 

Initiative, on the other hand, is not included in the default hierarchy level. However, initiatives are essential when working with Portfolio for Jira. Typically configured at a higher level than epics, initiatives are the high-level priorities that multiple teams or departments work against in an organization or company. Initiatives can span multiple epics, projects, and teams, and the work for initiatives can last months and even years.

As both Portfolio for Jira and  Jira are highly customizable, you can also customize hierarchy levels to fit the needs of your team. You can also define the relationship between the issue types in Jira and the hierarchy levels in Portfolio for Jira. You can create unlimited hierarchy levels, and customize the names for the levels as necessary.

Creating new hierarchy levels in Portfolio for Jira

  1. Go to Portfolio (in header) > Administration > Portfolio Hierarchy Configuration.
  2. Click + Create Level.
  3. Enter a name for the level, and then map the new level to a Jira issue type.

次の点に注意してください。

  • You can remove a level by clicking Remove correspondingly.
  • You can't remove epics, stories, and sub-tasks, since these comprise the default hierarchy level in Portfolio for Jira.
  • Similarly, you can't rearrange epics, stories, and sub-tasks, as these are part of the default hierarchy level. You can rearrange other custom levels by drag-and-drop, as needed.

イニシアチブ レベルを複数のプロジェクトに追加する

An issue can live in a single Jira project. However, if your organization is working on several projects, you might want to consider having your initiative to span multiple projects.

If you're working with cross-project initiatives, you can create a dedicated Jira project, where the cross-project initiatives are stored, and then use the project as an issue source in your plan.

  1. Create a Jira project that will hold your initiatives.
  2. Jira アプリケーション >  > [課題] に移動します。
  3. Click Add issue type.
  4. Create a new issue type called Initiative, and set it as Standard Issue Type, and then click Add.
  5. [課題タイプ スキーム] > 対象のプロジェクト > [編集] の順にクリックします。
  6. イニシアチブ課題タイプを、対象のプロジェクトの課題タイプにドラッグ アンド ドロップします。
  7. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  8. Click more () next to the plan name > Configure > Issue sources.
  9. Select your new project as an issue source.
  10. Go to Portfolio (in header) > Administration > Portfolio Hierarchy Configuration.
  11. Click + Create Level and create the new initiative level.
  12. Click Apply > Save changes.

イニシアチブ レベルを 1 つのプロジェクトに追加する

プロジェクトで階層レベルを増やす必要があり、イニシアチブを複数のプロジェクトに横断させる必要がない場合は、使用するプロジェクトだけにイニシアチブ レベルを追加する選択ができます。

この方法は、プロジェクト内で階層レベルを増やす必要があり、イニシアチブをプロジェクト横断して使用することはほとんどない場合に使用できます。

  1. Jira アプリケーション >  > [課題] に移動します。
  2. Click Add issue type.
  3. Create a new issue type called Initiative, and set it as Standard Issue Type, and then click Add.
  4. [課題タイプ スキーム] > 対象のプロジェクト > [編集] の順にクリックします。
  5. Drag and drop the initiative issue type to the issue types for your project.
  6. Go to Portfolio (in header) > Administration > Portfolio Hierarchy Configuration.
  7. Click + Create Level and create the new initiative level.

  8. Click Apply Save changes.

  9. If your team doesn't want to see the initiatives in your Jira board, you can configure the board filter to exclude initiatives from the board. You can then create a new filter that only includes the initiatives, and then add that as an extra source to your plan.

  10. イニシアチブを持つ両方のプロジェクト、および、エピックやストーリーを含む他のプロジェクトまたはボードに、プランを接続します。

Mapping Jira issue types to Portfolio for Jira levels

Multiple issue types can be mapped into each hierarchy level. You can map Jira stories, bugs, and tasks into custom Portfolio for Jira levels.

Keep in mind that the following configuration will be applied to all plans.

  1. Before mapping a Jira issue type into Portfolio, make sure that the issue type has been created in your Jira application instance. You can learn more about creating issue types here.
  2. Once you've created your new issue type in your Jira application, it's time to map it into Portfolio for Jira.
  3. Go to Portfolio (in header) > Administration > Portfolio Hierarchy Configuration.
  4. Choose the issue types you want to configure from the drop-down menu, then map them into to the hierarchy level you want, and then click Apply.
  5. Click Save changes.

これで、プランの範囲ビューで新しい構成レベルで作業できるようになりました。


最終更新日 2018 年 4 月 3 日

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

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