Using scope and dependencies

How to configure the issue details from the scope section

The scope issue details view allow you to see the details of each issue, such as progress, dependencies, and start and end dates.

  1. Go to your plan > Scope and select an issue.
    The details view opens up.

  2. From here, you can add the issue to an existing initiative and you can add new dependencies between issues.
フィールド 説明
Shows the parent issue
説明 Issues description
Dependencies Issues relationships and dependencies
Earliest start Defines the earliest date it can be scheduled for.
Scheduled start The start date produced by Portfolio schedule calculation.
Scheduled end The end date produced by Portfolio schedule calculation.

How to add dependencies between issues

This feature allows you to set scheduling dependencies between issues.

  1. Go to your plan > Scope > and click the issue name.
  2. Click + Add dependency,  add the relation between issues and select Add dependency.
    Once you've added the new dependencies. You can commit the changes to Jira.
    Before committing the dependencies to Jira Software, make sure you have the Link Issues permission turned on in your Jira admin space. 

Circular dependencies

It often happens that you have dependencies between sub-tasks. Whenever this happen, you'll get an error at the story level.

Inherited dependencies

When you have dependencies between your issues, you can see the relationship from the schedule by clicking the timelines with a lighter blue. When you click them, you will get a new window with the issue keys that the issue is related to. However, when you have inherited dependencies, which means that there are dependencies between the children of two different parents,  and you check the relationships at the Epic level. The pop up window won't give you the issue keys because, the dependency exist between children.

In this case, the dependency was set between two stories from different Epics.


 例

You have an issue called "list existing trips" that depends on both the frontend framework and the backend framework being in place. You will add a dependency so the frontend framework work must happen before listing the existing trips is implemented.

  1. Go to your plan > Scope > and click List existing trips.

  2. Add two dependencies as follows:



    As a result, list existing trips will be scheduled after the two dependencies. Once you've added the new dependencies. You can commit the changes to Jira.

    注意

    Before committing the dependencies to Jira Software, make sure you have the Link Issues permission turned on in your Jira admin space.


最終更新日 2018 年 1 月 31 日

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

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