Derive Schedule from Polarion Plans

When to Use This Approach

Use plan-derived scheduling when work items do not have their own start/end date fields populated but are assigned to Polarion Plans (iterations, releases) that have defined date ranges. This is common in agile workflows where sprints and iterations define the schedule.

Gantt chart showing a user story whose schedule is derived from its assignment to a Polarion Plan instead of from date fields

User story PCP-43 assigned to Iteration 34, with its Gantt schedule taken from that sprint assignment

Add the Item Script

Navigate to Widget Properties > Advanced > Item Script and add one of the following scripts depending on your scenario.

Option A: Derive Schedule for All Unplanned Items

Use the built-in utility method to automatically assign plan dates to unplanned work items:

if (wi != null) {
  if (task.unplanned) {
    task.deriveScheduleFromPlans(wi, "iteration");
  }
}

Replace "iteration" with the plan template ID that matches your project (e.g., "release", "sprint").

Unplanned Work Package 'The Primary Flight Displays' shown on the Gantt chart before its schedule is derived

The Work Package planned in Iteration 39, which ends on 10.10.2023

Polarion Plan view confirming Iteration 39 and its end date used as the source for the derived schedule

Option B: Derive Schedule for a Specific Plan Type

For more control, iterate through the work item’s plan assignments and match a specific template:

var plans = wi.getPlannedIn().iterator();
while (plans.hasNext()) {
  var plan = plans.next();
  if (plan.getTemplate().getId() === "Iteration") {
    task.start_date = util.getDate(plan, "startDate");
    task.end_date = util.getDate(plan, "dueDate");
    task.duration = null;
    task.readonly = true;
    task.unplanned = false;
  }
}

Property	Effect
`task.start_date`	Sets the task start from the plan’s start date
`task.end_date`	Sets the task end from the plan’s due date
`task.duration = null`	Clears duration so it is computed from dates
`task.readonly = true`	Prevents manual editing of derived dates
`task.unplanned = false`	Marks the item as scheduled on the Gantt chart

Always wrap your Item Script with if (wi != null) to prevent errors when the script processes synthetic or missing work items. Without this check, the script may fail silently.

Set the derived dates with task.start_date and task.end_date (property assignment, as shown above) — this is the documented form (see the Item Script API). Do not assign to task.setStart_date / task.setEnd_date: those are setter methods, not assignment targets, so assigning a value to them does not set the date. For the Polarion 2304+ scripting changes (getter methods and typeof checks), see Migrate Scripts for Polarion 2304+.

Configure the Plans Gantt View (Optional)

If you want to display both plans and work items together on a single Gantt chart, use the Plans Gantt widget:

Set Widget Properties > Show Plan Work Item > Enable Show Items to true.
Configure the Load Children depth to control how many levels of sub-plans and work items are displayed.
Set the child link role to load work items under their parent plans.

For portfolio-level visibility, configure the Plans Gantt with Release as the top-level plan template, Iteration as the second level, and work items as the third level. Set Load Children to 3 to display the full hierarchy.

Save and Reload

Save the widget properties and reload the page. The Gantt chart recalculates work item positions based on their plan assignments.

When to Use This Approach

Option A: Derive Schedule for All Unplanned Items

Option B: Derive Schedule for a Specific Plan Type

Verification

See Also

​When to Use This Approach

​Option A: Derive Schedule for All Unplanned Items

​Option B: Derive Schedule for a Specific Plan Type

​Verification

​See Also

When to Use This Approach

Option A: Derive Schedule for All Unplanned Items

Option B: Derive Schedule for a Specific Plan Type

Verification

See Also