Using scope and dependencies

お困りですか?

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

コミュニティに質問

This page discusses the usage of Portfolio for Jira live plans (any version from 2.0 to 2.27). If you're using the redesigned planning interface, see this page instead.

In the scope details view, you can see the details of each issue, as well as add scheduling dependencies to issues.

The following information are displayed in the scope details view, for each issue:

フィールド説明
Shows the parent issue
説明 Issues description
DependenciesIssues relationships and dependencies
Earliest startDefines the earliest date it can be scheduled for
Scheduled startThe start date produced by Portfolio schedule calculation
Scheduled endThe end date produced by Portfolio schedule calculation


To view issue details in the scope details view:

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click the Scope tab to display the scope table.
  3. In the scope table, click an issue. The details view will display.


To add a scheduling dependency to an issue:

Before you begin, make sure you have the link issues permission in your Jira instance. 

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click the Scope tab to display the scope table.
  3. In the scope table, click the issue to which you want to add a scheduling dependency.
  4. Click + Add dependency, then specify the relation between the issues.
  5. Celect Add dependency.
  6. Commit the changes back to your Jira instance.


To illustrate, let's say you have an issue called List existing trips, and this issue depends on both the frontend framework and the backend framework being in place. You then need to add a dependency, so the frontend framework work must happen before listing the existing trips is implemented.

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click the Scope tab to display the scope table.
  3. Click the List existing trips issue.
  4. Add two dependencies to the issue, as follows:

    As a result, the List exisiting trips issue will then be scheduled after the frontend framework and backend framework issues.
  5. Commit the changes back to your Jira instance.

関連トピック

最終更新日 2019 年 9 月 20 日

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

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