Skip to main content

Field Mapping Parameters

Valid Field Combinations

You must configure at least two of the three date-related fields. The Gantt calculates the missing field from the other two.
diagram
If only one date field is mapped, the Gantt cannot calculate task scheduling. Tasks will appear at default positions without correct date representation.
For production use, configure proper Polarion custom fields with the recommended types:
If a mapped custom field does not exist in Polarion, the Gantt automatically creates and uses a String ad-hoc custom field. While functional for testing, ad-hoc fields lack type validation and are not recommended for production use.

Duration Precision

The Duration Precision parameter switches the entire Gantt between day-based and hour-based scheduling:
Switching to High (Hours) precision changes the date format across the entire Gantt instance. All date fields display time components, and durations are stored in hours. See Schedule in Hours Instead of Days.

Administration Defaults

Default data mapping values for new Work Items Gantt widget instances:

Configuration Example

A typical data mapping for a project using custom Polarion Date fields:
  • Start Field: plannedStart (Date field)
  • End Field: plannedEnd (Date field)
  • Duration Field: gantt_duration (Integer field)
  • Progress Field: gantt_progress (Float field)
  • Duration Precision: Standard (Days)
With this mapping, the Gantt reads start and end dates from the plan fields, calculates duration automatically, and tracks progress via the float field.

Plans Gantt Data Mapping

When Show Plan Work Item is enabled in the Plans Gantt, an equivalent set of data mapping fields appears for the work items displayed under each plan: These follow the same rules and field type requirements as the Work Items Gantt data mapping.

See Also

Last modified on July 10, 2026