When I move a milestone, why don't all the sub-tasks move with it?

[Crabby]

I have a project file with two milestone groups; each milestone has a few
mini-projects, and each mini-project has a handful of tasks. I am trying to
have milestone #2 start w.r.t. the end of milestone #1, and when I establish
the link, all but one of the mini-projects shifts its start-date accordingly.
The only thing about the non-conforming mini-project that's different is
that it has one task that it has one task that can't start until a task in
another miniproject in the same file and milestone group is completed.
Otherwise, all the tasks and the mini-projects start ASAP, without constraint.

 

[Crabby]

Hi Reid,

Thanks for your help, first off!

Now, moving to what I hope is the same terminology you use, I have a
summary task, indented under which are a handful of summary tasks, each with
their own tasks. Now, why the top level summary task moves the start date of
some but not all other indented summary tasks, despite everything being ASAP
and having no constraint date, remains my mystery. Moving a summary task is
supposed to move the tasks within it, if they are configured that way, no?

 

[Jan De Messemaeker]

Hi,

I simply can't "move" a summary task, I have no access to start nor finish
fields nor does it move on the graphical side.

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
+32-495-300 620

Hi Reid,

Thanks for your help, first off!

Now, moving to what I hope is the same terminology you use, I have a
summary task, indented under which are a handful of summary tasks, each with
their own tasks. Now, why the top level summary task moves the start date of
some but not all other indented summary tasks, despite everything being ASAP
and having no constraint date, remains my mystery. Moving a summary task is
supposed to move the tasks within it, if they are configured that way, no?

constraint.

 

[Reid McTaggart]

Moving a summary task is supposed to move the tasks within it,
if they are configured that way, no?

No. A summary task does not necessarily have any influence on the tasks
that underly it. More the opposite: A summary task's duration, start, and
finish change to match the durations, starts and finishes of its underlying
tasks.

The task you see that does not seem to behave as you want is doing what it's
doing because it has a predecessor that is outside of the summary task you
are looking at. That is actually good scheduling, because generally it is
not good to link summary tasks.

 

[Jan De Messemaeker]

Hi again,

I really cannot reproduce this problem.
Moving the start of the top level summary task moves all the summaruies
below (at least when calculation is on automatic).
I'd really like to see the error.
HTH

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
+32-495-300 620

Hi Reid,

Thanks for your help, first off!

Now, moving to what I hope is the same terminology you use, I have a
summary task, indented under which are a handful of summary tasks, each with
their own tasks. Now, why the top level summary task moves the start date of
some but not all other indented summary tasks, despite everything being ASAP
and having no constraint date, remains my mystery. Moving a summary task is
supposed to move the tasks within it, if they are configured that way, no?

constraint.