Company-wide configuration
Jira administrators have to specify the company-wide app settings, setup default values for new Gantt charts, and configure Jira fields that are used by Gantt Suite.
The app configuration is accessible from Administration → Apps → Gantt Suite → Configuration:
 |
Configuration
Gantt settings
|
Gantt settings that are defined in Gantt Suite configuration, are the default values for all new Gantt charts to be created.
Here, Jira administrator can select the default fields for the task start and/or task end, and the task deadlines.
Quick tip: By hovering over a label with a question mark, you can read more details regarding that particular setting. Please see an example below.
|
Security
|
|---|
Jira administrators can configure newly created charts to be private, public, or have restricted access by default.
Calendars
Starting with app version 9.0.x, the Resource tab has been renamed to Calendar, where users can configure calendars to be used as the default for both the Main Chart and User Calendars
|
|---|
|
|---|
In addition, a Chart Manager can also manage Global Calendars. Define calendars once and reuse them across multiple charts
|
|---|
Please refer to Examples: Using Global Calendars in Gantt Suite for Jira for more details.
Links configuration
|
The values defined here by Jira administrator are the default values for all new Gantt charts.
Basically, the same configuration regular Jira users will see when creating a Gantt chart. If needed, the defaults can be overridden. Links configuration tab
Starting app version 2.1.x, a direction can be defined for a configured link, either outward or inward. For instance, link Duplicate has inward direction is duplicated by and outward direction duplicates.
|
Task progress
Jira admins define a default Time tracking mode.
|
In case your team does not track time in Jira, you may want to select the option No Time tracking to make it a default behavior for all new Gantt charts.
Auto-Scheduling
The Auto-Scheduling tab in Gantt Suite Configuration allows administrators to define how task scheduling is handled across all charts.
Administrators can enable Auto-Scheduling by default, ensuring that new charts automatically apply scheduling logic when created.
If Auto-Scheduling is enabled by default, administrators can also enable Initial Auto-Scheduling, which triggers scheduling automatically the first time a chart is opened.
Exclusion Rules
The Exclusion Rules section allows administrators to define conditions under which specific tasks are excluded from automatic scheduling.
Administrators can configure default exclusion rules that apply to all new charts.
Rules can be created based on various supported fields, such as the Status field, for example, allowing fine-grained control over which tasks are included or excluded from auto-scheduling.
Multiple conditions can be combined using logical operators OR or AND to build complex rule sets.
Administrators can easily edit or delete default exclusion rules at any time.
|
|---|
Example:
As an administrator, you can define default exclusion rules for auto-scheduling to skip:
Tasks with status Done, Resolved, or Closed
Tasks with a due date before the start of the current year
Steps:
Check the box next to Exclusion Rules.
Click Add.
Select Status, choose operator IN, and set values Done, Resolved, Closed.
Click Next, then Add OR Condition.
Select Due Date, choose operator <, and set function startOfYear().
Click Next, then OK, and finally Save.
|
|---|
The company-wide configuration for default auto-scheduling can be adjusted by chart managers to meet their specific needs and preferences for each Gantt chart. https://brizoit.atlassian.net/wiki/x/FQAoKwE
Extended settings
In addition, starting the app version 3.0.c, admins can define default extended chart settings such as Default unit for resource workload, etc.
|
If needed, the option Allow internal task creation can be hidden by default for all new charts to be created.
|
|---|
Quick tip: To make some custom markers appear in Gantt chart by default, use the next template below and adjust it to your needs.
[{"date": "2023-12-25 00:00", "title": "Christmas", "color": "green"}, {"date": "2024-01-01 00:00", "title": "Happy New Year!", "color": "red"}]
Permissions
In addition to the app configuration, Jira admins configure the app permissions such as the app visibility, chart creation, screen field check and impersonated view.
|
App visibility
By default, all Jira users are granted permission to see "Gantt" in Jira top menu and access the app. Select specific groups in case you want to restrict the app access.
Chart creation
By default, all Jira users who are granted "App visibility" permission can create a Gantt chart. Select specific groups in case you want to limit the chart creation ability.
API token creation
By default, no one can generate an API token. Select the groups you wish to grant this permission to.
We strongly recommend using groups specifically created for generating API tokens in Gantt Suite. This allows Jira administrators to easily remove a user from the group if an API token is compromised.
Screen field check (in Server/Data Center versions)
This settings was added to the app’s server version, starting v2.2.x.
By default, there is no verification if configured field is present on project's screens.
Therefore, a user might be able to set a value for a field that is configured for Gantt chart but is not present on Create/Edit issue screens of configured project.
Should you prefer to prevent such behavior, please make sure to check the checkbox 'Screen field check'.
Allow impersonated view
The expected behavior is that Jira user without a permission to access a project will not see its tasks on a chart. This setting lets chart creators to allow users with restricted access to see the project tasks on a chart in a read-only mode. In other words, it allows users with restricted access to see a chart the way chart owner does.
When this company-wide setting is turned on, and a chart creator also turned impersonation on, the app impersonates as chart creator for Jira issues and links loading. All other operations are NOT using impersonation.
The existing Gantt charts aren’t affected by the changes made in company-wide configuration with the exception for Screen field check and Allow impersonated view which are not the default values. Both settings affect all Gantt charts, existing and new ones.
User settings
Jira admin can define the default user setting for all new Gantt Suite users. If needed, they can be overridden by the app users, according to their business needs.
|