In order for the dates to cascade, you cannot set dates manually on the successor tasks. This will override the system calculations and prevent the dates from shifting. If you create a series of tasks, set durations for each, and link them with finish to start dependencies... then all you need to do is chance the date or duration of the first task in the sequence to see the others shift.
Post
FollowWorking with dependencies and due dates
I want to prove that the product will cascade date changes on all dependent tasks when the start date for a predecessor task is delayed, but I cannot. I created two tasks in the milestone of a test project, making the first one start on 1/1, end on 1/31 (duration 23 days), while the second one started on 2/1. I then made the second one FTS-dependent on the first. When I change the start date for the first to 1/20, the target date for that task is properly auto-adjusted based on the duration, but the start date for the second remained at 2/1. What do I have to do to get the start/target dates for dependent tasks to reflect the change in the predecessor task?
Please sign in to leave a comment.
1 comment
Date
Votes
Comment actions