Dependencies are a valuable tool for indicating the order in which tasks or project phases should be completed. Dependencies can be set at the Task, Subtask, and Milestone levels.

A task or subtask dependency can be established from the Dependency option found within an open task or subtask.

When a task or subtask dependency is set, it will display a padlock icon over the Complete tickbox and a caution tape-style header. This header will also indicate the nature of the dependency that has been set.

Subtasks can be dependent on either tasks or subtasks.

Tasks and subtasks locked due to a dependency can be edited and updated, but cannot be marked as complete until the Task they depend on is completed. Assigned users will be notified when a dependent Task is unlocked and available.

When a Task has a dependency, its start and due dates will adjust in bulk by the same number of days as the dependent Task. For example, if the Task "Information Architecture" depends on "Kickoff Call," both Tasks will have their dates adjusted together. Note that this cascading effect applies even if the Tasks are not part of a Milestone on a Roadmap.

Similarly, subtasks that are part of the dependency chain will have their due date updated the same amount of days that their dependency task's or subtask's due date is updated.

When the due date of Kickoff is extended, the start and due dates of Information Architecture are moved by the same amount of days.

This effect can take place through multiple Tasks. In the below example, each Task is dependent on the last (Page Content → Gather Requirements → Information Architecture → Kickoff.) Changing the due date of Kickoff call will cause all of these Tasks to update their start and due dates in a cascade. This is called a Dependency Chain.

Note that cascading is only based on the changing due dates, so you can start Tasks before the Task they are dependent on is completed.