Gantt fields

Gantt fields are a set of default fields provided by Gantt Suite for Jira.

Native Gannt fields

Certain Gantt fields, such as Flags, Mode, Duration, Baseline start, Baseline end and Baseline delay are native app fields which do not exist in Jira. They represent information which is not available in Jira or supplement it using default values.

Duration field derives its default value from Extended settings in the chart configuration when no duration is specified for the task during its creation.

On Cloud, Duration is stored internally and doesn’t have a corresponding custom field in Jira. However, it can be shown on the issue details page by means of Start field and End field specified in the chart configuration.
In Data Center version, Duration has a corresponding Jira field which is added to the project screens by default.

For charts based on agile scheduling mode, duration is an internal field. Duration of tasks is derived from duration of backlog and sprints they belong to.

Baseline start, Baseline end and Baseline delay fields have been introduced in the app version 5.0. They are only applicable when a baseline is selected.

Gantt fields that can sync with Jira

Start date, End date, Deadline and Resource fields are based on Jira fields which are configured in the chart configuration.

image-20240515-095123.png
image-20240515-095218.png

Start date

For Jira tasks, Start date field is synced with and corresponds to the custom Jira field specified in the chart configuration (eg. Start Date [Gantt]). However, it can differ for parent tasks in bottom-up mode. In such case, the app calculates Start date based on the task’s child issues in the chart rather than the task’s own value in Jira.

Please note that Start field is not required in charts with ‘By task end’ scheduling mode. In such case, Start date values of Jira tasks are stored internally and are not sent to Jira.

For internal tasks, Start date is an internal Gantt field unrelated to Jira.

End date

For Jira tasks, End date field is synced with and corresponds to the custom Jira field should it be specified in the chart configuration (eg. End Date [Gantt]). Please note that End field is not required in charts with ‘By task start’ scheduling mode. In such case, its values are stored internally and are not sent to Jira.

Should the End field be provided in the chart configuration, its values for Jira tasks will correspond to Jira with the exception of parent tasks in bottom-up mode. In such case, the app calculates End date based on the task’s child issues in the chart rather than the task’s own value in Jira.

For internal tasks, End date is an internal Gantt field unrelated to Jira.

Please note that for charts with agile scheduling mode, Start date and End date are internal Gantt fields whose values are derived from the Backlog and Sprint dates and are not synced with Jira.

Deadline

Deadline field is only available when it is specified in the chart configuration.

For Jira tasks, it corresponds to the configured custom Jira field. For internal tasks, Deadline is stored internally and isn’t sent to Jira.

Resource

Resource field is only available when it is specified in the chart configuration.

For Jira tasks, it corresponds to the configured Jira field. For internal tasks, Resource is stored internally and isn’t sent to Jira.

Key, Summary, Description

For Jira tasks, Key, Summary and Description fields correspond to the same system fields in Jira.

For internal tasks, they are internal Gantt fields unrelated to Jira.

Original estimate

Original estimate field correspond to the Original estimate field in Jira when time tracking is enabled in the chart, except for parent tasks in bottom-up mode. In such case, the app calculates Original estimate based on the task’s child issues in the chart rather than the task’s own value in Jira.

Remaining

Remaining field corresponds to the Remaining Estimate field in Jira unless progress overrides are used in the chart. In such case, Remaining field is calculated based on Progress field.

Spent

Spent field corresponds to the Time Spent field in Jira when time tracking is enabled in the chart. Otherwise, Spent is calculated based on Progress field.

Work

Depending on the chart configuration, Work field can be based on dates only and be equal to task duration, or can rely on the combination of Jira fields such as Original estimate, Time spent and Remaining estimate.

To find out more about Work field, please refer to the following page: Task duration calculation explained | How exactly task work and task duration are calculated?.

Progress

Depending on the chart configuration, Progress field can be calculated based on Jira fields Time spent and Remaining estimate, can be overridden based on a status, or entered manually. Please note that for parent tasks in bottom-up mode Progress is calculated based on the task’s child issues in the chart, except for when a Progress value for the parent task has be entered manually.

 

You will see Gantt fields in the table columns, filters and conditional colors stylized as plain text as opposed to Jira fields which use italics.

Â