Configure advanced Gantt chart behavior to match your team's planning process. The Extended Settings tab provides optional settings for scheduling, workload calculation, task creation, visualization, and resource planning.

Most users can work effectively with the default settings. These options are intended for teams that need more control over how Gantt Suite behaves.

What you can configure

The Extended Settings tab allows you to:

Configure default scheduling values.
Customize the Edit Task dialog.
Control workload calculations.
Configure custom chart markers.
Define estimate aggregation behavior.
Configure automatic conflict resolution.
Customize overload calculations.
Enable or disable internal task creation.

Scheduling defaults

Default unit for the Edit Task dialog

Specify the default unit that Gantt Suite uses when users enter a numeric value without a unit in the Edit Task dialog.

For example, if the default unit is days, entering:

5

will be interpreted as 5 days.

Default task duration

When a newly created task has no scheduled duration, Gantt Suite assigns the default duration configured here.

The duration can be entered using a human-readable format, for example:

1w
3d
8h
1w 2d 4h 30m

Default resource workload unit

Select the default unit used to display workload in the Resource Panel.

For example:

Hours
Days
Weeks

This setting affects only how workload is displayed.

Task visualization

In-cell task disposition

This option controls how tasks are displayed inside calendar cells.

Enabled

Tasks occupy the entire cell when their duration equals or exceeds the working time for that day.

Disabled

Tasks occupy only the portion of the cell that corresponds to their scheduled working hours.

Custom chart markers

In addition to the standard Today, Sprint, and Release markers, you can create your own markers to highlight important dates.

Examples include:

Company holidays
Product launches
Milestones
Deadlines
Internal events

Custom markers are configured using JSON.

Example:

[
  {
    "date": "2023-12-25 00:00",
    "title": "Christmas",
    "color": "green"
  },
  {
    "date": "2024-01-01 00:00",
    "title": "Happy New Year!",
    "color": "red"
  }
]

Estimate aggregation

Include Jira sub-tasks into parent estimate

This option controls whether estimates from Jira sub-tasks are included in their parent issue's estimate.

It is especially useful when parent tasks are configured in Manual scheduling mode.

Typical use cases include:

Showing the total work of a Story, including all of its sub-tasks.
Rolling up Story and sub-task estimates to Epics.
Controlling which hierarchy levels display aggregated estimates.

Example 1

Include Story estimates and their sub-tasks in the Epic estimate.

Configuration:

Enable Include Jira sub-tasks into parent estimate.
Story uses Manual mode.
Epic uses Bottom-up mode.

Result:

The Epic displays the combined estimate of the Story and all of its sub-tasks.

Example 2

Aggregate only sub-task estimates into their Story without affecting the Epic.

Configuration:

Enable Include Jira sub-tasks into parent estimate.
Story uses Manual mode.
Epic also uses Manual mode.

Result:

The Story displays the combined estimate of its sub-tasks, while the Epic continues displaying only its own estimate.

Automatic conflict resolution

Tasks may occasionally contain conflicting Work and Duration values.

Enabled

Gantt Suite automatically resolves scheduling conflicts.

Disabled

When the chart is opened, users are prompted to choose how each conflict should be resolved.

For more information, see the Conflict Resolution documentation.

Workload distribution

Choose how task work is distributed across the task duration.

Note: On Jira Data Center and Server, this option is available only when Jira Time Tracking is enabled.

Remaining work distribution

Remaining work is distributed from today until the task's end date.

Previously logged work remains distributed across the elapsed portion of the task.

If the calculated completion date differs from the scheduled end date, Gantt Suite suggests resolving the scheduling conflict.

This mode is useful when teams regularly log work during task execution.

Note: Work logged today is included in the remaining work calculation beginning at 12:00 AM the following day.

Uniform workload distribution

The total task workload (Time Spent + Remaining Estimate) is distributed evenly across the entire task duration.

This is the traditional workload calculation used by Gantt Suite.

Resolving conflicts

When selecting Resolve, Gantt Suite updates the chart immediately.

Only changes selected for saving are written back to Jira.

If you are working within a Scenario, the changes remain inside the Scenario until you choose to publish them to Jira.

Resource overload calculations

Additional settings allow you to control how resource and team overload indicators are calculated.

Period overload / availability

Choose how overload is evaluated within each reporting period.

Total

Workload and availability are calculated for the entire period.

An overload indicator appears only when the total workload exceeds the total available capacity.

Daily

Workload is evaluated day by day.

If a resource is overloaded on any day within the period, the entire period is marked as overloaded.

Use Daily when identifying short-term workload peaks is important.

Example: Period overload / availability

The Period overload / availability setting determines how resource overload is evaluated for each reporting period.

Total

Resource workload and availability are calculated for the entire period. An overload indicator is displayed only if the total workload exceeds the total available capacity during that period.

Daily

Resource workload and availability are evaluated day by day. An overload indicator is displayed if the resource is overloaded on at least one day within the selected period.

Example

The screenshots below show the daily workload of the user Henry Pride.

Henry Pride works 8 hours per day, 5 days a week, for a total weekly capacity of 40 hours. In this example, he is overloaded only on the first day of week 21.

When Period overload / availability is set to Total, the weekly workload is not highlighted in red because Henry's total workload for the week is 34 hours, which does not exceed his weekly capacity of 40 hours.

When Period overload / availability is set to Daily, the weekly workload is highlighted in red because Henry is overloaded on at least one day during week 21 (May 20).

Team overload indicator

Choose how team overload should be calculated.

Team

The team is considered overloaded only when the team's total workload exceeds the team's total capacity.

Per user

The team is marked as overloaded whenever at least one team member is overloaded.

Note: Team capacity calculations are always based on the configured team capacity, not on the chart calendar or individual user calendars.

Internal task creation

Gantt Suite supports creating internal tasks, which exist only within the chart and are not created as Jira issues.

You can control whether users are allowed to create these tasks.