Milestone Completion Tracking

[bauer172uw]

Our group uses milestones as predecessors to certain tasks within our
project. These milestones are successors of work within our project. We
have noticed that after our resources have completed their work which are
predecessors to these milestones, the milestone still needs to be manually
updated to 100% complete. We have tried using fixed work and fixed units but
both have still required us to manually update the milestone. Does anyone
know if there is a way to have your milestones update to 100% complete as
their predecessors are completed?

Thank You for any help.
Mike

 

[Dale Howard [MVP]]

Mike --

You must manually mark milestones as 100% complete. Sorry. That's just the
way the software works.

 

[Roger C.]

In my organization, we assign a resource to a milestone in order to designate
accountability for completion of the work. Our resources report their time
through PWA, where we are using managed time periods. However, it seems that
we can't make an assigned milestone complete through PWA (can't report time
against a task that has no duration!), and trying to mark it complete
manually through Project Pro always gives us the "out of synch" warning.
Synching, then wipes clean the complete status, and not synching doesn't
update new time reported for other working tasks. Seems that I missed
something in training. Can anyone help?

Thanks,
Roger
Cincinnati

 

[Roger C.]

Oh - just found a similar thread - and will check out the hotfix mentioned
first.
R.

 

[Gary L. Chefetz \(MVP\)]

Roger:

Go to SP1 for Project Server and Project

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-

 

[Master Chief]

Hi,

Gary or Dale,

We're experiencing the same issue as Roger C. We have SP1 in our Client and
Server environments. When manually closing milestones all completed task
still reopen.

Roger C. mentions in the thread above there's a Hotfix for this issue. Does
anyone have any information on this Hotfix?