Dependencies exist to capture the order in which work needs to happen: which Tasks, Milestones, or Constraints have to start or finish before another can move forward. Because dependencies are stored at the Project level, they aren't just visual lines on one Workspace; they're relationships tied to the underlying records, so they show up wherever the connected elements appear and get validated automatically. When dates end up conflicting with a defined relationship — for example, a successor scheduled to start before its predecessor finishes — that conflict is flagged as a warning right on the connection, giving your team a clear, consistent signal of where the sequencing has broken down, regardless of which Workspace they're looking from.

-
Hover over your desired predecessor element
-
Click and drag the dot that follows your cursor across the top of the card and drop it over your desired successor element
- Click on the line to open the dependency menu to change the dependency type, appearance, adjust lag or lead times, or delete it
You can also add Connections through the Editor's Connections Page so you can skip drawing the line directly.
-
Double-click on a Task to which you want to add a dependency
-
Click on the dropdown on the top left corner of the Editor and open the Connections page
-
Click on the +Add button on the bottom right corner
-
Click on the Add: dropdown to decide if the connection you wish to add is a parent, successor, or predecessor relationship
-
Click on the Target dropdown and type in the title of the Task, Milestone, or Constraint you wish to connect
- Click the Add button
✏️ Note: If you have multiple Plans in the Workspace, these dependencies may appear across the Plans, especially in the case of cloned cards.
Dependency Types
There are four different dependency types that you can program between elements:
- Finish to Start (FS) — the successor cannot start until the predecessor finishes; the default dependency type in Workspaces
- Start to Start (SS) — the successor cannot start until the predecessor starts
- Finish to Finish (FF) — the successor cannot finish until the predecessor finishes
- Start to Finish (SF) — the successor cannot finish until the predecessor starts

-
Click on the dependency between elements
-
Click on the FS button
- Click on the new dependency type you wish to use
The rules of the dependency type will now be enforced, so adjusting the elements in a way that breaks the rules mentioned above will cause the two connected elements to be in a conflicted state. The dependency will also appear in the Editor's Connections page.

Click on this article to learn how to resolve these conflicts: Resolve Scheduling Conflicts
Lag & Lead

-
Click on the dependency between elements
- In the open field next to d Lag, type in your desired number of days
- A positive number is a lag time
- A negative number is a lead time
-
Press the Enter/Return key on your keyboard to confirm the change
- Anytime the designated lag or lead is broken in any Project Workspace, the conflict warning will appear for you to resolve
Comments
0 comments
Article is closed for comments.