Resolving Cyclic Dependencies in Gantt Suite

In certain cases, cyclic dependencies between Jira issues can prevent the Gantt chart from loading correctly or from performing auto-scheduling as intended.

A cyclic dependency arises when tasks are linked in a way that forms a closed loop—either directly or indirectly—making it impossible to determine a valid execution order. These loops may occur due to parent-child relationships or through configured dependency types.

Example of a Cyclic Dependency:

• Task A has to be started after Task B

• Task B has to be started after Task A

In this case, Task A cannot start until Task B does, and Task B cannot start until Task A does. This circular relationship creates a deadlock with no viable starting point for scheduling.

To enable accurate scheduling, such cyclic dependencies must be identified and resolved, as auto-scheduling in Gantt Suite for Jira cannot proceed when these loops are present.

How to Detect Cyclic Dependencies Using the Browser Developer Console

To identify Jira issues involved in cyclic dependencies:

1. Open the developer console in your browser (press F12 or right-click and select Inspect).

2. Navigate to the Console tab.

3. In the filter/search field, type: cyclic

4. The console will display messages listing the issues involved in cyclic dependencies.

Review the issue keys and their relationships, and adjust the task links to break any circular chains.

Open

Open