Skip to main content

​
Prerequisites

  • Nextedy GANTT installed and configured with dependency roles
  • Polarion administrator access to edit workflow configurations
  • Dependency links already established between work items

​
How the Condition Works

The Gantt workflow condition checks all work items linked to the transitioning item via specified dependency link roles. If any linked predecessor is not in one of the allowed status states, the workflow transition is blocked. diagram
The condition is aware of Gantt dependency types. For forward-link checking, items connected via start-to-finish or start-to-start dependency types are excluded from the check because they do not need to finish first. Only finish-to-start dependencies are enforced in the forward direction.

​
Step 1: Open the Workflow Configuration

  1. Navigate to Administration > Work Items > Workflow
  2. Select the work item type whose workflow you want to modify
  3. Locate the transition where you want to add the dependency gate

​
Step 2: Add the Workflow Condition

  1. Click on the target transition to edit it
  2. In the Conditions section, add a new condition
  3. Select the Gantt Dependencies Status Condition from the list of available conditions

​
Step 3: Configure the Condition Parameters

The condition accepts the following parameters:
ParameterTypeRequiredDescription
link.rolesString (comma-separated)At least one of link.roles or back.link.rolesLink role IDs for forward-linked work items to check
back.link.rolesString (comma-separated)At least one of link.roles or back.link.rolesLink role IDs for back-linked work items to check
valid.statesString (comma-separated)YesWork item status IDs that linked items must be in for the condition to pass

​
Configuration Example

To require all predecessors (via the depends_on link role) to be in done or closed status before a work item can move to in_progress: 
link.roles=depends_on
valid.states=done,closed
To check both forward and backward links: 
link.roles=depends_on
back.link.roles=depends_on
valid.states=done,closed
The valid.states parameter accepts Polarion status IDs (e.g., done, in_progress), not the human-readable display names (e.g., “Done”, “In Progress”). Check your workflow configuration for the correct status IDs.

​
Step 4: Understand the Forward vs. Backward Check

  • link.roles checks items that the current work item links to (forward direction)
  • back.link.roles checks items that link back to the current work item (reverse direction)
Use link.roles when your dependency links point from the dependent item to its predecessor. Use back.link.roles when links point from the predecessor to the dependent item.
The condition runs with elevated system privileges, ensuring that dependency gates are enforced even when the current user cannot see all linked work items. Hidden links cannot bypass the status gate.

​
Verification

You should now see:
  • When attempting to transition a work item whose predecessors are not in the allowed states, the transition is blocked with a validation message
  • When all predecessors meet the status requirements, the transition proceeds normally
  • The condition respects dependency type semantics, only enforcing finish-to-start dependencies in the forward check

​
See Also

KB ArticlesSupport TicketsSource Code
  • prod-gantt-src/com.nextedy.polarion.gantt/src/com/nextedy/polarion/gantt/workflow/GanttLinkedWorkItemsStatusCondition.java
  • prod-gantt-src/com.nextedy.polarion.gantt/src/META-INF/hivemodule.xml
  • prod-gantt-src/com.nextedy.polarion.gantt.client/cypress/e2e/Rewritten Tests/testGanttCreatePlan.cy.ts
  • prod-gantt-src/com.nextedy.polarion.gantt/src/com/nextedy/polarion/gantt/instructions.html
  • prod-gantt-src/com.nextedy.polarion.gantt.client/src/index.html