Dependencies
Dependencies turn a Gantt into a real schedule. By linking issues with predecessor-successor arrows, you tell Foundation that one piece of work must come before another — and the schedule engine keeps them in sequence when dates shift.
Use dependencies when the order between tasks matters: a design must finish before development starts, integration tests can only run after both components are ready, or deployment waits on a final approval.
The four dependency types
Section titled “The four dependency types”Foundation supports all four standard types. You pick the type when you draw the link.
| Abbreviation | Name | Meaning |
|---|---|---|
| FS | Finish-to-Start | Successor starts when predecessor finishes. This is the default. |
| SS | Start-to-Start | Successor starts when predecessor starts. |
| FF | Finish-to-Finish | Successor finishes when predecessor finishes. |
| SF | Start-to-Finish | Successor finishes when predecessor starts. |
FS is by far the most common. Use SS, FF, or SF for parallel work or rolling handoffs.
Draw a dependency
Section titled “Draw a dependency”- Hover over a bar in the Gantt. Small dependency handles appear on the bar’s left and right edges.
- Click and hold a handle, then drag to the bar you want to link to.
- Release the mouse over the target bar. The edge you leave from and the edge you land on determine the type:
- Right edge → left edge = FS
- Right edge → right edge = FF
- Left edge → left edge = SS
- Left edge → right edge = SF
- An arrow appears between the two bars. Foundation writes the underlying Jira link so collaborators see the dependency in Jira too.
Inspect or change a dependency
Section titled “Inspect or change a dependency”- Click the arrow between two bars. A Dependency popover opens.
- The popover shows the type and any lag time (positive = delay, negative = lead).
- Change the type or lag, or click Remove to delete the dependency.
Lag is measured in working days — Foundation skips weekends when enforcing it.
Auto-scheduling when a predecessor moves
Section titled “Auto-scheduling when a predecessor moves”Foundation’s schedule engine is forward-only: when you drag a predecessor later, successors cascade forward to keep the constraint satisfied. This includes sync agent runs, Rovo mutations, bar drags, and grid date edits. Successors do not automatically move earlier — if you want to pull them in, edit them directly.
During a drag, translucent ghost bars preview where successors would land so you can see the cascade before you commit. When the move completes, a toast summarizes what shifted and lets you undo within 60 seconds.
Cycles and conflicts
Section titled “Cycles and conflicts”- Foundation rejects a new dependency that would create a cycle (A → B → A) before it saves.
- If a date edit puts two linked items into conflict, the bar shows a warning. You can choose to auto-schedule (clear the conflict) or respect the link (move the date).
- If cascades start ping-ponging — rescheduling the same issues repeatedly — Foundation halts after a few passes and warns you to check dependency rules.