Configuring scheduling settings

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.

The schedule is one of core capabilities of Portfolio for Jira. The scheduling algorithm will automatically assign teams to issues, take dependencies and priorities into account, and generate a realistic forecast.

The timeline view shows forecasted release dates, and allows you to break things down based on projects, teams, and team members.

You can configure the following items to get the most out of the scheduling algorithm of Portfolio for Jira.



  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click more () next to the plan name > Configure > Scheduling.
  3. 警告レベルに対し、次のいずれかのオプションを選択します。
    • Errors only — Only errors will be displayed in your plan if any issue happens 
    • エラーと警告 - プランで問題が発生した場合、エラーと警告の両方が表示されます。
    • なし - プランで問題が発生した場合、メッセージは表示されません。


The following table lists the available planning mode settings.

Planning unit

プランで作業項目を見積もる際に使用する単位。プランの計画単位として、日、時間、またはストーリー ポイントから選択します。

Sprint length

プランで設定されたすべてのチームに対するスプリントの既定期間。既定では、スプリントの長さは 2 週間に設定されます。

Default weekly capacityThe team's overall capacity in a work week, and is only used if there are no team members defined in that particular team
Unestimated item scheduling

Defines how any unestimated work items will be handled in the plan:

  • Base on default estimates — Across all hierarchy levels, the defined default estimates will be applied to all work items that have no children in the hierarchy configuration.
  • Base on target dates  Portfolio for Jira will schedule unestimated work items to last the duration of their assigned sprint, release, or target date.
  • Custom — The start and end dates of unestimated items will be based on the custom dates (which come from custom fields previously configured) that you set. If you don't set these custom dates, the start and end dates will then take the default values of target start and target end dates, correspondingly.
  • Off — Portfolio for Jira will ignore any unestimated items, and these items will have no impact on the schedule.

For more information about the options, see Scheduling unestimated items.


  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click more () next to the plan name > Configure > Scheduling.
  3. 必要に応じて、計画モードの設定を構成します。

スケジューリング オプション

次の表は、利用可能なスケジュール オプションの一覧を示します。

スケジューリング オプション説明
Issue assignee import level
  • Defines the hierarchy level up to which Portfolio for Jira will try to match the assignee of an issue to the corresponding member of the team. You can specify the level at which the issue assignees in your Jira application are indeed the people who will actually work on the issues.
  • For example, you might have the Product Manager assigned to an epic, and individual developers assigned to the stories within that epic. In reality, the Product Manager won't really be the person working on the stories, since it will be the developers themselves. You can then set the issue assignee import level to story, in this case. the will then take the story assignees into account, but not the epic assignees.
  • Sub-task is the default option enabled.
Maximum assignees per story

個々のストーリーで作業するために割り当てることができるユーザーの最大数を定義します。既定では、ストーリーごとに最大 3 人の担当者が設定されます。

Dependency scheduling


  • 依存関係のある作業項目を必須項目の下にランキング (既定で有効化)
  • 必須の作業項目を依存する項目よりも上にランクする
  • オフ


Dependent story constraint
  • On (enabled by default) — Prevents work items with dependencies from being worked on at the same time. The work items will be scheduled in different sprints for Scrum teams, and different days for Kanban teams.
  • オフ — 依存関係を持つ作業項目に同時に取り組むことができます。


Enforce concurrent work

次のオプションは、1 つの作業項目に複数のメンバーが割り当てられている場合にのみ適用されます。

  • On (enabled by default) — The scheduling algorithm of Portfolio for Jira will ensure that the work for that issue will be scheduled into a single sprint.
  • Off — Portfolio for Jira will schedule the work of the assigned team members whenever there is free capacity, thereby allowing the work item to span multiple sprints.
Stage sprint constraint
  • On (enabled by default) — The separate stages of a work items will be scheduled sequentially into different sprints.
  • オフ — 1 つのスプリント内で、1 つの作業項目が複数のステージを横断して並行して発生する可能性があります。
Minimum work package size

The minimum work in story points for all work items above the story level in the hierarchy configuration of Portfolio for Jira. By definition, work items above the story level would be considered high-level work — which is typically broken down into stories. By setting the minimum work package size, you can avoid filling up any free capacity with work items that are unrealistically small.

  • To make Portfolio for Jira schedule high-level work as realistically as possible, set the minimum work package size to the estimate of a small story.
  • To purposely fill your capacity to the maximum, set the minimum work package size to 0.
  • デフォルトでは、5 ストーリー ポイントが最小の作業パッケージ サイズとして設定されます。

プランのスケジューリング オプションの設定方法

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click more () next to the plan name > Configure > Scheduling.
  3. Configure the scheduling options as necessary.


How do I keep assignee and team member in sync between Jira and Portfolio for Jira?

You can do this as long as you have boards as an issue source.

Jira から担当者を取り込む方法

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.

  2. Click more () next to the plan name > Configure > Scheduling.

  3. Set the 'issue assignee import level' to the hierarchy level that you want to get the assignees from.

担当者が、プランの課題ソースであるボードに関連付けられたチームメンバーである場合、そのチーム メンバーが自動的に割り当てられます。

チーム メンバーを Jira に反映させる方法

  1. コミット オプションを構成していることを確認します。

  2. プランの変更を Jira にコミットします。

If a single team member is assigned to an issue in Portfolio for Jira, then the team member will be the assignee of the corresponding issue in Jira.

最終更新日 2019 年 7 月 28 日


Powered by Confluence and Scroll Viewport.