Problem with milestones as predecessors

Last post 10-23-2008 1:57 PM by Andrew Gross. 2 replies.

Page 1 of 1 (3 items)
	Sort Posts: Previous Next

10-23-2008 1:41 PM

Andrew Gross
Joined on 01-31-2008
New York City
Posts 37

Problem with milestones as predecessors

Reply Contact

If milestone "A" is the predecessor to task "B" and task "B" is set to start "as soon as possible" and task B has no other predecessors then task B will be set to start either today or tomorrow...even though milestone A may be scheduled for any number of days out. Looks like a bug to me.

Anyone come up with a workaround?

Filed under: dependency, milestone, scheduling

10-23-2008 1:49 PM In reply to

Steve Thompson
Joined on 02-25-2006
Seattle, WA
Posts 429

Re: Problem with milestones as predecessors

Reply Contact

Set a lead in time of -1. Try that.

Steve Thompson | Solutions Consultant
Daptiv

10-23-2008 1:57 PM In reply to

Andrew Gross
Joined on 01-31-2008
New York City
Posts 37

Re: Problem with milestones as predecessors

Reply Contact

Thanks Steve, but that unfortunately does not remedy it. I do, however, use the "-1" lead time to another task to make sure "B" doesn't start too early, i.e. task "AA" below.

So what I have setup is

Task "AA"

Milestone "A"

Task "B"

Milestone "A" has task "AA" as a predecessor". I wanted to link task "B" to "A" per the first post. But since this doesn't work, I link "B" to "AA". When "B" is linked to "A", A's finish date is ignored.

AEG

Page 1 of 1 (3 items)