Task dependencies

With task dependencies, you can mark a task as waiting on another task.

Dependencies are the relationships among tasks which determine the order in which activities need to be performed.

Teams with collaborative workflows can easily see what tasks they’re waiting on from others, and know when to get started on their portion of work.

When the first task is completedcompleted To mark a task with a checkmark to indicate that it is done. Read more , it will notify the assigneeassignee The person responsible for the task or subtask. Asana allows one assignee per task or subtask. Read more of the next task that they can start on their task.

Dependencies are available to all Premium, Business and Enterprise customers.

Mark tasks as dependent on

The indication banner will only appear in the dependent task’s right pane.

Shortcut to dependencies

If you’re finding it difficult to locate a specific task or it doesn’t appear in the dropdown list, just copy and paste the URL link of the task instead.

Drawing dependencies on your Timeline

You can set dependencies directly on your Timeline by clicking the connector icon that appears when hovering over a task and then dragging to another task.

Multiple dependencies

A single task can be dependent on multiple tasks and multiple tasks can be dependent on a single task.

To remove a dependency, hover over an existing indication banner and click the X symbol that appears.

Notifications

The assigneeassignee The person responsible for the task or subtask. Asana allows one assignee per task or subtask. Read more of the dependent task will receive notifications for the following actions:

• The precedent task is marked completecomplete To mark a task with a checkmark to indicate that it is done. Read more
• The precedent task has its due datedue date The date that a task or subtask is due. Read more changed or removed

If a task is dependent on multiple tasks, you will only receive one notification when all precedent tasks have been completed.

Auto-shifting dates for dependent tasks

Dates for precedent and dependent tasks can automatically be updated if a change occurs that results in an overlap in the dates of any of the tasks. This can be done from your timeline view. This feature automatically skips weekends. You also have the option to turn off auto-shifting dates.

For auto-shifting to work it is necessary that:

• A task has been marked as dependent to another
• The precedent and dependent tasks have due dates set. It can also work if tasks have start dates set along with a due date
• The change in any of the tasks causes an overlap in the dates
• The date change has been made on Timeline. If the update on a task is made from My Tasks, Inbox, or any other project view that is not Timeline (like List, Board or Calendar), the affected tasks won’t be automatically updated.
• Tasks are marked as not complete. Changes in dates will not have an impact on completed tasks

This functionality does not apply to subtasks by default. You can mark subtasks as dependent on the parent task if you want to use auto-shifting for subtasks.

How auto-shifting dates work

You can use auto-shifting while updating dates from your project Timeline.

Auto-shifting dates will work for precedent and dependent tasks:

• A change on a precedent task’s date will update the date of dependent task when it causes an overlap.
• A change on a dependent task’s date will update the date of precedent task when it causes an overlap.

Any change to start date as a result of the auto-shifting dependency dates feature also changes the due date of that same task (and vice-versa).

The auto-shifting dependency dates feature automatically skips weekends. In addition, it works for changes that move the dates back or forward:

• When a date is pushed forward in the future, a precedent task can move dependent tasks forward as well. However, if the date of a dependent tasks is postponed, it will not affect the precedent tasks.
• When a date is pushed back in the past, a dependent task can push a precedent task back as well. However, if the date of a precedent task is moved back, it will not affect the dependent tasks.

Tasks can be marked as dependent of tasks that are themselves depending on other tasks, as well. Auto-shifting dates will also work for tasks under those dependency chains. In addition, milestones and subtasks will be updated too if they are part of a dependency chain.

Examples of auto-shifting in action

A precedent task has a due date of August 4th. It has two depending tasks: the first one has a due date of August 8th, while the second one has a due date for August 14th.

A precedent task has a due date of August 4th. It has two depending tasks: the first one has a due date of August 8th, while the second one has a due date for August 14th.

A precedent task has a due date of August 4th. It has two depending tasks: the first one has a due date of August 8th, while the second one has a due date for August 14th.

Turning off auto-shifting dates

Date shifting is set for Premium Asana teams and Organizations by default. If you wish to prevent dates from being automatically updated, you can turn it off for specific projects from your Timeline view.