Task %Complete at 99%

[fefe78]

Hi everybody

I have the following issue with Project Server 2003.
Once an activity is set to completed (setting the amount of work)
through PWA by a resource , when I go (as a manager) to accept the
changes and PWA opens Project Professional, the task activity %complete
is at 99%.
This behaviour is not the same for all tasks, as a matter of fact other
tasks reach correctly 100%.
I don't undestand why a few tasks behave differently from others.
I noticed that in 99% tasks the Actual Finish date is not set.

Is that a bug or a wrong task setting in project plan?

Thanks to everybody.

Bye

 

[brantleyd]

Do you have the resource assigned to a Summary Task in your project plan?
This would cause the behavior you are seeing.

 

[fefe78]

No,

There isn't any resource assigned to a summary task.
Even under the same Summary, some tasks are 100% complete while other
are 99%.

brantleyd ha scritto:

 

[Jeff T]

I ran into this as well.
My senario was that the lowest # task that I tried to get to 100% that had a
cost of 0 ( I think that was the problem) would not go to 100% complete.

All the OTHER tasks that were higher than that task would go 100% complete
(I'm not talking about summary tasks, just str8 line tasks)

I had to "fake" out project inorder for it to work.

 

[fefe78]

What do you mean by "fake out project"?

Jeff T ha scritto:

 

[Jeff T]

I put in a "dummy task" at task #1 that had the same characteristics of the
task that wouldn't go 100%, then the rest would go to 100%.

 

[fefe78]

I made the same thing at the beginning... but I'm trying to understand
why. I compared both two tasks, the correct one and the wrong one... and
unfortunately I didn't find any differences.
The problem is that in new plans sometimes it happens and I have to
force my customers to correct the task manually.
Has someone found that this is a Microsoft bug, so I can reply that it
is not my fault?

Bye

Jeff T ha scritto:

 

[Gary L. Chefetz [MVP]]

I've seen similar behavior when milestones are not set to 100% complete, or
there is work associated with milestones.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Christina]

I have seen this as well and have found that sometimes it is a result of
"rounding". Meaning, say you have a task that has 40 hours of work amongst 7
people. If the work is evenly distributed, each person is "scheduled" for
5.7142... hours of work. It will show in their timesheet as 5.71 hours of
work. Although I wouldn't expect a resource to enter that they worked 5.71
hours on this task, I have resources who have done that (whole other training
issue). None the less, when they enter 5.71 hours, the % Complete changes to
100 on their timesheet and Remaining work changes to 0. However, the task in
the project shows 99%. I took a look at the task assignment in the database
and saw that the Remaining Work on that task for that person was NOT 0. In
fact, it was .0042.

I don't know if that is the situation you are running into, but it's a
thought.

Christina