値を親課題にまとめる

お困りですか?

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

コミュニティに質問

For parent issues, you can choose to display a preview of the rolled-up values of the child issues in several fields in a plan. The rolled-up values will appear with a roll-up arrow icon beside them. Note that the rolled-up values are just a preview, and you can still change these values if needed.

You can roll up the following values: estimates, teams, sprints, and releases.

Sample plan with team values being rolled up, from child issues to parent issues

To roll-up values in a plan:

  1. In your plan, click the View settings drop-down.
  2. [ロールアップされた値をフィールドに表示する] チェックボックスを選択します。

プランでの見積りの集計

課題の見積りが、子課題から親課題に集計される場合は、以下の点に注意してください。

  • Rolled-up estimate values are rounded up to only one decimal place for story points, and two decimal places for hours and days.
  • The rolled-up value of a parent issue will display 0 if work has been logged for its estimated child issues, and there's 0 time remaining for the child issues.
  • 子課題が見積もられていない場合、見積もりフィールドは空白のままとなります。見積値がないため、親課題の集計見積もりには影響しません。

Rolling up dates in a plan EARLY ACCESS

  • The content in this section only applies if you've enabled roll-up dates as an early access feature in Portfolio for Jira. Once the early access feature is enabled, you can then enable roll-up dates in each plan where you want to use them.
  • Enabling rolled-up dates in a plan doesn't directly change any date values. With roll-up dates, you have a view of the child issue dates rolling up to the corresponding parent issues.
  • Being an early access feature, this is still work-in-progress. The feature may be incomplete, or may change before becoming fully incorporated in Portfolio for Jira. Send us any feedback and suggestions you may have via the give feedback button in your plan.

Once enabled, the dates of direct child issues will roll up onto its parent issue if the following takes place:

  • you haven't explicitly set a start date or end date for the parent issue, and
  • 親課題をスプリントに割り当てていません。

Sample plan with roll-up dates setting enabled

Sample plan with teams and dates rolled up to the parent issues

上記のプランの例では以下を確認できます。

  • Both team values and date values of child issues are rolled up to the parent issues, and the values are displayed with the roll-up arrow icon.
  • The parent initiatives and epics that don't have start and end dates, or both dates now display differently:
    • Initiative PM-1 now displays a roll-up date for its start date, with the roll-up arrow icon as well. Its schedule bar in the timeline appears differently, with the start date side displaying in yellow stripes, and the end date side displaying in solid yellow. This is because PM-1 has a rolled-up start date and an explicitly set end date. The schedule bar is colored yellow because the issues in the plan are colored by status.
    • Since epics IOS-9 and ADR-1 don't have explicitly set dates, then they're now displaying roll-up dates from their child issues. Their dates display with the roll-up arrow icon, and their schedule bars are displayed in stripes colored by status.
    • Since epic ADR-19 has an explicitly set start date but no end date, it now displays a roll-update for its end date. Its schedule bar displays the start date side in solid blue, and the end date side in blue stripes.
    • Since epic ADR-18 has explicitly set start and end dates, the date values remain the same, and the schedule bar displays in solid blue.

日付の集計の仕組み

Roll-up dates function and adhere to the following:

集計は、プランで使用されている開始日と終了日に対して動作する

Roll-up dates operate on the configured start and end dates of a plan. These are the dates that are being used to schedule the issues in the plan itself. These dates include the following:

  • Target dates, which are the default type of dates being used to schedule issues in a plan
  • Custom dates, as long as they are of the date picker custom field type, and have been configured to be the start and end dates in a plan. The custom date columns will be displayed with the date lozenge ().
  • Sprint dates, if the plan has been configured to use sprint dates for issues that don't have start and end dates. The sprint dates for each issue will be displayed with the sprint lozenge ().

Roll-up dates are consistently used as regular issue dates throughout Portfolio for Jira. This means that the dates are used all across the plan, from scheduling the issues in the plan to triggering warnings for any misaligned dates.

集計対象となる最下層のレベルはストーリー レベルである

The sub-task level is the lowest hierarchy level in Portfolio for Jira. The story level is then the lowest hierarchy level where date roll-up from sub-tasks can then happen.

Sample roll-up of sub-task dates to story dates

上記の例では、以下のことに注意してください。

  • 親ストーリー ADR-2 には子サブタスク ADR-22 があります。
  • ADR-22 has explicitly set start and end dates, which roll up to its parent story ADR-2.

子課題に開始日と終了日がない場合でも集計が行われる

子課題に開始日と終了日がない場合も、親課題での集計は行われます。子課題で欠落している日付は無視され、日付の集計は他の子課題の既存の日付に基づきます。

Note that for roll-up to happen in this situation, the parent issue must have at least two child issues, and one of them should have start and end dates. If all the child issues of a parent issue don't have any dates, roll-up will not happen. If a parent issue has only one child issue and it doesn't have any dates, roll-up will not happen as well.

日付を持たない子課題での集計の例

上記の例では、以下のことに注意してください。

  • 親エピック ADR-8 には、Android Sprint 1 および Android Sprint 3 のスプリント日を使用している子課題があります。
  • 子ストーリー ADR-9 はスプリントに割り当てられていないため、スプリント日を使用していません。ADR-9 にも、明示的な開始日と終了日がありません。
  • 引き続き、親エピック ADR-8 で日付の集計が行われます。ADR-9 で欠落している日付は無視され、集計日は他の子課題の開始日と終了日に基づきます。

Partial roll-up may happen for parent issue dates

部分集計は、いずれかの課題の日付が設定されていないに発生する可能性があります。これが発生した場合は 2 つのシナリオが考えられます。

親課題に 1 つの日付が明示的に設定されていて、もう片方の日付が集計値の場合

親課題に 1 つの日付が明示的に設定され、もう片方の日付が子課題から集計されている場合、親課題のスケジュール バーは部分集計と表示されます。

Sample partial date roll-up, with explicitly set start date and rolled-up end date

上記の例では、以下のことに注意してください。

  • 親エピック ADR-8 には、Android Sprint 1 および Android Sprint 3 のスプリント日を使用している子課題があります。
  • ADR-8 には開始日が明示的に設定されていますが、終了日は子課題の日付から集計されています。

子課題で 1 つの日付が明示的に設定されておらず、もう片方の日付がまったく設定されていない場合

If a child issue does have one date explicitly set, be this the start date or end date, then the schedule bar of the parent issue will display a partial roll-up, and the roll-up will fade out towards the side of the missing date. This missing date prevents Portfolio for Jira from determining a roll-up date, and thus the roll-up fades out.

終了日を持たない子課題がある場合の、部分的な日付ロールアップの例

上記の例では、以下のことに注意してください。

  • 親エピック ADR-8 には、Android Sprint 1 および Android Sprint 3 のスプリント日を使用している子課題があります。
  • The child story ADR-9 is not assigned to a sprint, and is therefore not using any sprint dates. However, ADR-9 has an explicitly set start date, but no end date. The schedule bar on the timeline is displayed in solid blue at the start side, but the bar's color gradually fades out.
  • Partial date roll-up happens for the start date of the parent epic ADR-8. There's no end date value, but the roll-up icon still displays, to indicate that partial roll-up is happening. With the schedule bar displaying in roll-up stripes, the bar's colored stripes also gradually fade out towards the end date.

Child issue dates have an impact on rolled-up parent dates

If a parent issue has rolled-up dates, and you explicitly set the dates for one of its child issues, the dates of the parent issues will adjust accordingly but will still retain its rolled-up state.

Sample plan with parent epic having rolled-up dates

上記の例では、以下のことに注意してください。

  • The parent epic IOS-9 has child issues using sprint dates.
  • The child issue dates roll up to the parent epic itself, which is why the its schedule bar is in blue stripes.

IOS-17 の終了日を後に移動すると、次のようになります。

  • IOS-17 の終了日が 2020 年 2 月 6 日に変更されました。
  • 親エピック IOS-9 も新しい終了日 (2020 年 2 月 6 日) を継承します。
  • Since the parent epic's dates are rolled-up from its child issue dates, the schedule bar will remain in blue stripes.

子課題の日付は、明示的に設定された親課題の日付には影響を与えません。

As long as you've enabled roll-up dates as an early access feature in Portfolio for Jira, the dates of child issues will no longer have an impact on the dates of its parent issues.

For example, if a child issue's end date goes beyond its parent issue's end date, the parent issue's end date will not be pushed out, and will remain as is.

親エピックに明示的な日付が設定されているプランの例

上記の例では、以下のことに注意してください。

  • The parent epic IOS-9 has child issues using sprint dates.
  • IOS-9 has explicitly set start and end dates, specifically 7 Feb 2020 as its end date.
  • Even if roll-up dates are enabled, IOS-9 will be using the dates that have been explicitly set for it. This is why its schedule bar is in solid blue color.

IOS-17 の終了日を後に移動すると、次のようになります。

  • IOS-17 now has a new end date of 19 Feb 2020, which triggers a warning that the child issue end date goes beyond the parent issue end date.
  • Even if roll-up dates are enabled, the parent epic IOS-9 will still be using the dates that have been explicitly set for it.
  • IOS-9 will still have its end date as 7 Feb 2020, and its schedule bar will remain in solid blue color.

This behavior only applies if you've enabled roll-up dates as an early access feature in Portfolio for Jira. If you haven't enabled the early access feature, see Scheduling issues to know how child issue dates impact parent issue dates.


Roll-up dates respect the configured view settings in a plan

Roll-up dates respect the group and color settings that have been configured in a plan.

Sample plan with issues grouped by projects, colored by labels, and having rolled-up dates

上記の例では、以下のことに注意してください。

  • The issues in the plan are grouped by projects, with the issues in the Android App project appearing in the top swimlane.
  • The issues are also colored by labels, with the schedule bars accordingly colored by the labels set for each issue.
  • The epic ADR-8 has two labels, design and documentation, so its schedule bar is displaying the colors set for both labels.
  • ADR-8 の日付は子課題から集計されているため、スケジュール バーも色付きのストライプで表示されます。
最終更新日: 2020 年 2 月 20 日

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

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