You must configure at least two of the three date-related fields. The Gantt calculates the missing field from the other two.
Combination
Start Field
End Field
Duration Field
Behavior
Start + Duration
Required
Not set
Required
End date calculated from start + duration
Start + End
Required
Required
Not set
Duration calculated from date range
End + Duration
Not set
Required
Required
Start date calculated from end - duration
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:
Field
Recommended Type
Ad-Hoc Fallback
Notes
Start Field
Date (Only)
String
Date fields provide native date picker in Polarion
End Field
Date (Only)
String
Date fields ensure proper date validation
Duration Field
Integer
String
Integer provides numeric validation
Progress Field
Float
String
Float supports decimal precision (0.0 - 1.0)
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.
The Duration Precision parameter switches the entire Gantt between day-based and hour-based scheduling:
Mode
Duration Unit
Date Format
Use Case
Standard (Days)
Days
Date only
Sprint planning, release scheduling
High (Hours)
Hours
Date + Time
Fine-grained task scheduling, shift planning
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.
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.
