How can I add a dependency to my project?

 

This article describes functionality of our new project module. This module is being rolled out gradually, so it is possible you do not have access to the features described here yet. If that is the case, you can still find documentation on the previous project module here.


Dependencies let you define the order in which tasks and groups in a project need to be completed. When a task or group is blocked by another, it cannot be started, or marked as done, until the blocking work is finished. This keeps your project timeline realistic and prevents your team from accidentally working on things in the wrong order. Discover all about project dependencies here!
 

What are project dependencies

Dependencies are useful any time one task can't move forward until something else is done first. Examples:

  • A design that needs to be approved before development can start;
  • A customer needs to deliver assets (logo, copy, photos) before the website build can start;
  • A budget needs internal approval before materials can be ordered;
  • Training can only be delivered after the technical setup is done;
  • An invoice that can only go out once a project group is closed.
     

When dates change, all dependent tasks and groups shift automatically, you don't have to go through the project manually and update everything one by one. Team members are notified as soon as a blocked task becomes available, so everyone knows when they can get started without having to check in or wait for an update. Read more about notifications below.
 

Add a dependency

You can add dependencies to both tasks and groups from the work breakdown.
Note: Dependencies for meetings and materials are handled only in the context of moving dates in bulk in a project, e.g. when a group's dates change, materials in it move along. But you don't set an individual dependency directly on a single material or meeting line.

  1. Open your project and go to the Work breakdown tab.
  2. Click on a task or group to open its detail panel on the right.
  3. Scroll down to the Dependencies section and click on + Add dependency.

     
  4. In the dialog, you'll find the following options:
    • Dependency type: choose whether this item Is blocking another item, or Is blocked by another item.
    • Project line or group: select the task or group you want to link to.
  5. Click Add.
     

Notes: 

  • Dependencies are kept when you create a project from a template (at least when the checkbox next to ‘Dependencies’ is enabled in your project template) or when you duplicate a project.
  • It’s only possible to add dependencies within one project and not across different projects.
     

What you'll see once a dependency is set

Setting a dependency has two effects: it changes what you see in the work breakdown of your project, and it restricts what you and your team can do with blocked items.
 

In the work breakdown

Once a dependency is in place, a few things change in the Work breakdown view in your project:

  • Next to the group or task name, a small dependency icon appears. For items that are blocking another, the icon is grey. For items that are blocked, the icon is shown in red. This way, you can tell at a glance which groups or tasks are waiting on something else. Hover over the dependency icon to see what is blocking or being blocked.
  • For the individual tasks inside a blocked group, the Status column will show Blocked in red instead of their usual status. This makes it clear that those items cannot move forward until the blocking group or task is completed.
  • You can also filter the work breakdown on blocked items specifically. Click on Status and select Blocked to get an overview of everything that's currently waiting on another task or group to be completed first.
  • You can also see a task's dependency status directly from the task detail page. Open the task and scroll to the Dependencies section; it shows whether the task is blocking another item, or blocked by one.
     

Effect on blocked tasks and groups

While a task or group is blocked, you and your colleagues won't be able to:

  • Mark tasks as done*
    *Also; mark the group as done. A group becomes done automatically when all items are marked as done (including materials & meetings)
  • Track time on tasks
  • Move tasks forward in the kanban view; blocked tasks are clearly indicated and moved to the bottom of kanban columns.

     

What happens when dates change

When you update the start or end date of a group or task with a dependency, a dialog will appear to confirm the change:

 

Dependencies are always moved. For the underlying items, you can choose to enable the box next to ‘Update all underlying dates with X days’. This will move all underlying task dates within that group by the same number of days. You can disable the box if you only want to update the specific item without impacting the other items.
Note: Linked meeting dates won't be updated automatically when dates change.

If you use Planning, you'll also get a warning banner there when date changes affect your planned items. From there, you can choose to replan the affected items, delete them, or keep the current dates as they are.
 

Notifications

You'll receive an in-app notification and an email (if email notifications are enabled in Teamleader Focus) in two situations:

  • When the dates of a task or group (or both) you're assigned to change as a result of a dependency change. For example, because the blocking item's deadline was moved. 

     
    • You'll only receive this notification if someone else made the change, not when you update the dates yourself. 
    • If multiple tasks or groups in the same project are affected at once, these are bundled into a single notification.

       
  • When a task or group you're assigned to becomes unblocked, meaning the blocking task or group has been completed. This lets you know you can get started without having to check in or wait for an update. Again, if multiple items are unblocked at once, you'll receive one bundled notification per project.

     

Removing a dependency

To remove a dependency from a task or group:

  1. Open the task or group from the Work breakdown.
  2. In the detail panel, scroll down to Dependencies and click View dependencies.
  3. Click the bin icon next to the dependency you want to remove.
  4. Confirm by clicking Delete in the dialog.
     

Notes: 

  • Deleting a dependency is permanent. Once removed, all tasks associated with it are freed up immediately.
  • Moving/merging: If you move a task in the work breakdown or merge a group that has dependencies, a warning will appear before the action is confirmed. Any dependencies that conflict with the destination will be removed, and the remaining ones will be updated automatically.
  • Deleting a task or group that has dependencies: If you delete a task or group that is linked to a dependency, a warning will appear before the deletion is confirmed: all dependencies associated with that item will be deleted as well. You won't be able to keep the dependency in place once one of the linked items no longer exists.

Was this article helpful?