Skip to end of banner
Go to start of banner

Dependencies vs Milestones

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Dependencies are adjusted to account for the fact that a Milestone is a point in time (has a single date). Milestones don't artificially make the path between linked tasks longer. 

The calculation is affected when:

  • a Milestone is a target of a dependency

  • dependency is “start to end” OR “end to start”

Dependencies Leading to Milestones 

When a Milestone is a target of a dependency:

Task to Milestone OR

Milestone to Milestone

non-ASAP

ASAP

End → start

Milestone date >= task end date

Milestone date = task end date

End → end

regular dependency behavior

regular dependency behavior

Start → end

Milestone date <= Task Start Date 

Milestone date = task start date 

Start → start

regular dependency behavior

regular dependency behavior

"End to start" dependencies are adjusted to account for the fact that a Milestone is a point in time (has a single date).

When Milestone is a target:

  • ASAP - the Milestone date has to be the same as the source end date

  • non-ASAP - the Milestone date has to be the same or later than the source end date

"Start to end" dependencies are adjusted to account for the fact that a Milestone is a point in time (has a single date).

When Milestone is a target:

  • ASAP - the Milestone date has to be the same as the source start date

  • non-ASAP - the Milestone date has to be the same or later than the source start date

"End to end" dependencies behave normally.

"Start to start" dependencies behave normally.


Dependencies from Milestone to task 

Dependencies from Milestones to tasks behave normally (same as task → task dependencies).

  • No labels