このページの内容

関連コンテンツ

お困りですか?

The scope displays the core to-do list of your plan. I.e. all the work items in your plan. In this section, you can create new issues, and add and view other associated information such as estimates, releases, etc.

Epics - Large bodies of work comprised of multiple Stories.

Stories - Small bodies of work that represent product requirement. Multiple stories can be used to make an Epic.

Sub-task - Work components (i.e. tasks) that make up Stories.

You can configure your scope view following these simple steps:

Go to your plan > Reports > Switch report > Scope.

Select the elements that you want to see in the scope columns.Now you can see the selected elements in the main scope view.

Select the drop-down menu located on the right-hand side of the scope view to change which hierarchy level is being displayed.

Title

Issue title.

リリース

Releases the issue is assigned to.

Story Points / Estimates (h) / Estimate (d) *

Time estimate assigned to the issue. *Dependent on your chosen estimate type, you will see one of the three fields listed in the field column to the right.

If the original estimate assigned to an issue is changed over time, use this field to gain a historical reference of the original estimate.

*Dependent on your chosen estimate type, you will see one of the three fields listed in the field column to the right.

Earliest start date

The earliest start date refers to a user-specified date that is the earliest possible date an issue can be scheduled to start on. Click on the link below for further details on the earliest start date.

This user-specified date guarantees that an issue will not be scheduled before a defined date, even if it has higher priority relative to other issues, or there are free resources available.

Tip - Use "earliest start date" to account for external dependency

You can use the "earliest start date" to account for an external dependency that is not tracked in JIRA Software. Example: You've outsourced the user research and design work for a product to an external vendor. You know you can't start development until this work has been completed by the external vendor and handed over to your development team for the build. However, because they're an external team, you can't track their progress in JIRA - meaning you also can't add the external vendor's work as a dependency in Portfolio. Lucky for you, you know the completion date for the external vendor's work - 16/Oct/2016. You can use the external vendor's completion date to set the earliest start date for your team's development work - earliest start date of 17/16/2016 date to set the earliest start date. This earliest start date essentially acts in the same way as a dependency, dictating that your team's development work can't be started until after the user research and design work has been completed by the external vendor. In summary:

If external vendor's user research and design work is scheduled to be completed by 16/Oct/2016;

Set the earliest start date of your team's development work to 17/Oct/2016.

How does setting earliest start date on issues at various levels of your plan's hierarchy effect associated issues?

E.g. If I set the earliest start date on an epic, how does it relate to the stories within it?

The following points refer to the three earliest start dates pointed out in the scope table screenshot above.

Setting earliest start date on a parent issue: The earliest start date assigned to the parent (e.g. epic) applies to all stories within the epic. In the screenshot above, all the stories for epic "IOS-1 App Basics - iOS" will inherit the epic's earliest start date. Therefore, all the stories below the epic will only be scheduled by Portfolio from 17/Oct/2016 at the earliest.

Setting earliest start date on a child issue where the parent already has an earliest start date set: Setting an earliest start date on a child issue (e.g. story) will overwrite any earliest start date set on its parent issue. In the screenshot above, story "IOS-3 Setup dev and build environment" has had an earliest start date set to 25/Nov/16. This differs from the earliest start date for its parent epic, "IOS-1 App Basics - iOS" - 17/Oct/16. Therefore, the Portfolio ignores "IOS-3 Setup dev and build environment" parent epic's earliest start date and instead uses its story-specific earliest start date of 25/Nov/16 when scheduling. All of the other stories within the parent epic haven't had specific earliest start dates set, so Portfolio will continue to use the parent epic's earliest start date of 17/Oct/16 for scheduling. In summary, the following are the earliest start dates set for each of the stories within the "IOS-1 App Basics - iOS" epic and used by Portfolio for scheduling.

ストーリー

Earliest start date

IOS-2 As a user I can log into the system via Face...

17/Oct/16

IOS-3 Setup dev and build environment

25/Nov/16

IOS-4 Establish basic app dev framework

17/Oct/16

Setting earliest start date on a child issue where the parent has no earliest start date set: If the earliest start date is set on child issues (e.g. story) where the parent issue (e.g. epic) doesn't have an earliest start date, the earliest start date will only apply to the specific child issue. The parent issue and other child issues will not be influenced by the specific child issue's earliest start date. In the screenshot above, the earliest start dates set on the stories, "ADR-2 Establish basic app dev framework" and "ADR-3 Setup dev and build environment" will only apply to these two stories. In summary, the following are the earliest dates for the parent epic, "ADR-1 App Basics - Android", and each of the stories within it:

Epic/Story

Earliest start date

ADR-1 App Basics - Android

Not set

ADR-2 Establish basic app dev framework

30/Nov/16

ADR-3 Setup dev and build environment

01/Dec/16

ADR-4 As a user I can log into the system via Fac...

Not set

Target start

The date you’ve targeted to commence working on the issue. It has no impact on schedule calculation.

Scheduled start

The scheduled start date of the issue calculated from the provided data.

Target end

The date you’ve targeted to conclude work on the issue. It has no impact on schedule calculation.

Scheduled end

The scheduled end date of the issue calculated from the provided data.

チーム

Team name

Members

Team members

スプリント

Team members assigned to the issue.

Start date

Sprint start date

End date

Sprint end date

Initiatives

Initiatives are groups of epics. Think of them as higher-level business priorities or big projects potentially spanning multiple teams.

ラベル

Labels are keywords or tags that you can add to your tickets to categorize.

コンポーネント

Components are sub-sections of a project. They are used to group issues within a project into smaller parts.

テーマ

Show the themes assigned to each issue.

課題のステータス

Portfolio considers an issue "Completed" when it is assigned to any status of the "Done" category. For example, green category.