Cross-Project Predecessors

A Cross-Project Predecessor is a task that another task (called a successor task) in another project depends on. The predecessor is the task that takes priority over the dependent (successor) task. For example, you can create a dependency that requires that the predecessor task be marked Complete before the dependent task can start.

Like predecessors within a single project, Workfront allows for tasks to be dependent on tasks in other projects.

For example, if an excavating company has only one backhoe, and two concurrent projects have tasks that require the use of the backhoe, the project manager can make the task in the first project dependent on the task in the second project to illustrate that the excavating can start when the previous project will relinquish the backhoe. 

When linking projects through cross-project predecessors, the dates of the primary project (the one that has the predecessor task) will impact the secondary project (the one that has the successor task).

You must recalculate timelines of the projects in order to see dates updated for the secondary project. 
For more information on recalculating timelines, see "Configuring Timeline Recalculations for Projects."

For more information about predecessor relationships, see "Understanding Predecessors."

To create this type of predecessor-dependency relationship, create a cross-project predecessor that is tied to a dependent task in another project:

  1. Navigate to the task that will be your successor. 
  2. Click the Predecessors tab when viewing the task. (The Predecessors tab is usually in the More drop-down list.)
  3. Click Cross-Project Predecessors.
  4. Click Add Predecessor.

  5. In the Parent Project field, begin typing the name of the project that contains the task that you want to be dependent to your current task.
  6. Click the name when it appears in the drop-down list.
  7. In the Tasks field, begin typing the name of the task that you want to be dependent on your current task.
  8. Specify the following information for defining the relationship between the predecessor and dependent task:
    Dependency Type: Select the relationship that you want the task to have with the dependent task. The default relationship is 'Finish-Start,' meaning that the predecessor task must finish before the dependent task can start. For more information about the various dependency types, see "Dependency Types."

    Lag: Specify the amount of time that must pass after the completion of an enforced predecessor until the dependent task can begin. For more information about the various types of lag, see "Lag Types." [Does it have to be an "enforced" predecessor? What if the 'Enforced' box is unchecked?

    Enforced: When this option is selected, dependency relationship between the two tasks cannot be circumvented by users beginning tasks early. For example, if you enforce a relationship between Task A and Task B, Task B cannot be started until Task A is complete. For more information about enforcing predecessors, see, "Enforcing Predecessors."

    When this option is not selected, the dependency is treated like a suggestion to users. For example, users are able to start Task B before Task A is complete.
  9. Click Save.

    Tasks that have a cross-project predecessor display the reference number of the project the predecessor belongs to and the number of the task, separated by a colon in the Predecessors column on a task list.
    Mouse over this value, to get more information on the predecessor, the project and the dates.