Closed tasks changing to milestones

[DEY]

We are using project 2003. Managed time periods.
We have a project where the PM has to do this manual "uncheck" weekly --
Tasks keep getting flagged as "milestone", the PM does not want them to be
milestones! These are completed tasks that have 0 duration and 100% complete,
but were completed months ago.

How do we prevent this -- or is this just the way it works and we'll have to
live with it?

 

[Marc Soester]

Hi DEY,

There are 2 ways how you can "unmark" the task to not be a Milstone.
Your PM can double click the task and the Task Inforamtion dialog window
opens, under the "advanced" tab the PM can untick the Milstone and the task
will not be set as a Milestone anymore.

The second way is to insert the "Milstone" Column and mark the Task that
shouldnt be a Milestone as "no".
That should do the trick
Hope this helps

 

[DEY]

Thanks for the info-The PM's are aware of those solutions. The problem is
that these tasks are getting changed back to milestone EACH week even if zero
hours are reported against them. These tasks were closed back in March 2006
but they keep getting re-set back to milestones even after the PM's make the
manual change to "uncheck" the milestone flag.

 

[NoviceUser]

I am having this same issue and it seems that you have not received a
response. Where I have a task that had work and resources booked against it,
or a fixed cost task with no resources and the project was baselined, and
then subsequently the activity was not required so the remaining work was set
to zero or the fixed cost was zeroed, the task changed to a milestone
immediately.

If I uncheck the 'Milestone' checkbox in Task Information, and make the task
100% complete this seems to fix it, but only temporarily. At some later time
when I access the project again, these tasks have reverted back to milestones
and I have to manually chnage them back again.

This is also happening for one of our clients.

Can anyone advise if there is a solution or an alternative process. Our
client does not want their project managers to delete tasks so that is not an
option for us.

Thanks

 

[Conrad Santiago]

I'm curious for an answer on this question as well. We also use tasks with
zero-hour Work and check them off as "non-milestones". These tasks are
required to remain in our projects as non-milestones, however, every once in
a while, we open up the project only to find these tasks changed back to
milestones.

What causes them to change between the time these projects are checked-in
and then checked-out again? Is this something we can prevent from happening?

I noticed that when you copy and paste a zero-hour non-milestone task to the
same project or another project, the pasted task will change to a milestone.
However, that is the only way I've been able to recreate this change and even
then it only happens to the pasted task and not the other similar tasks in
the project.

Thanks in advance for any response.
Conrad Santiago