Dependencies and blockers
Represent work that must happen before other work can move forward.
Outcome
Use dependencies to make timeline movement reflect real sequencing constraints.
Applies to
Planners coordinating work across people or teams.
Before you start
Only add dependencies that affect schedule decisions. Too many weak dependencies make the timeline harder to reason about.
Steps
- Identify the issue that must happen first.
- Connect it to the issue that depends on it.
- Move the upstream issue and review the downstream impact.
- Remove dependencies that no longer represent real blockers.
- Recheck shared timelines after dependency changes.
What happens next
Dependency changes can affect dates and review expectations. Explain major changes in timeline comments when stakeholders are involved.
Related articles
Schedule workPlace issues on a timeline and adjust dates as the plan changes.MilestonesMark important dates and group timeline issues around delivery checkpoints.Dates changed unexpectedly on a timelineUnderstand why dates can move after edits, sync, or dependency changes.Linear integrationUnderstand how Linear works with Fluidwork timelines.