Skip to content
English
  • There are no suggestions because the search field is empty.

Dependencies

Some tasks cannot begin until others are completed. Dependencies provide a clear way to visualize and manage those relationships directly on your board so teams stay in sync and the sequence of work flows uninterrupted. 

When you select a tag in a multiday activity, you’ll see thin lines that are the color of the activity connecting the tags before and after. These lines indicate that the tags are already linked as part of the same ongoing activity and each tag is dependent on the previous task being completed. 

Note: Tags created as part of the same multiday activity are automatically linked with an inherent dependency. This reflects the natural sequence of work and cannot be removed. Only dependencies between different activities can be added or deleted manually. 

 Create a dependency between two tasks 

You can also link one task to another task that needs to be completed before the task can begin — it is dependent. 

  1. Click the activity tag where you want to start.
  2. A green icon will appear.
  3. Drag that arrow to the task this activity depends on.
  4. Release the arrow to create the link. A thick green line will appear, indicating the dependency.
  5. Dependency connections can be made to multiple tags. 

Note: A single task can have multiple dependencies. Use this feature to highlight complex handoffs between teams — like inspections or critical installations. 

Remove a dependency between tasks 

Need to adjust your plan? You can remove any manually created dependency: 

  1. Select one of the tags that’s part of the dependency.
  2. The dependency arrow will appear between the linked tasks.
  3. Click the trash can icon located in the center of the arrow.
  4. The dependency will be removed immediately. 

 

What happens to dependencies when things change? 

If a preceding task is delayed and pushed to a day later than the dependent task, you’ll see the dependency line turn red. This visual cue signals that prerequisite work hasn’t been completed and the dependent task is at risk of not being completed. A conversation might be needed so corrective action can be applied.