Links configuration tab
Configure how Gantt Suite maps Jira issue links to task dependencies and hierarchy relationships. Proper link configuration enables automatic scheduling, dependency management, and project hierarchy visualization.
What you can configure
The Links configuration tab allows you to:
Configure Jira link types used as scheduling dependencies.
Configure the hierarchy relationship between standard Jira issues.
Select which dependency types are available in Gantt charts.
Define the direction of each configured Jira issue link.
Dependency link types
Gantt Suite supports the four standard dependency types used in project scheduling:
Dependency type | Description |
|---|---|
Finish-to-Start (FS) | A successor task cannot start until its predecessor has finished. This is the most commonly used dependency. |
Start-to-Start (SS) | A successor task cannot start until its predecessor has started. |
Finish-to-Finish (FF) | A successor task cannot finish until its predecessor has finished. |
Start-to-Finish (SF) | A successor task cannot finish until its predecessor has started. This dependency type is rarely used. |
For each dependency type, select the Jira issue link that represents the relationship in your organization.
Recommendation: Most projects require only the Finish-to-Start (FS) dependency. Configure only the dependency types your teams intend to use to keep project planning simple and consistent.
Hierarchy relationship
The Hierarchy link type defines parent-child relationships between standard Jira issues.
For example, it can be used to represent:
Initiative → Epic
Epic → Story
Story → Task
Note: Jira sub-tasks are automatically recognized as children of their parent issue and do not require a configured hierarchy link.
Link direction
Starting with Gantt Suite 2.1.20, you can define which direction of a Jira issue link should be interpreted by Gantt Suite.
Many Jira link types have two descriptions, one for each direction.
For example:
Jira issue link | Direction |
|---|---|
duplicates | Outward |
is duplicated by | Inward |
Selecting the correct direction ensures that dependencies are created and interpreted correctly within the Gantt chart.
Best practices
For the most predictable scheduling behavior:
Configure at least one dependency type, preferably Finish-to-Start (FS).
Configure only the dependency relationships your organization actively uses.
Verify that the selected Jira issue links match your team's existing Jira workflow.
Use the Hierarchy relationship only for parent-child links between standard Jira issues.
|
|---|