Reassigning Task doesn't remove old resource

[LisaD]

We are using PWA 2007.

I re-assigned a task from the My Tasks page to another resource (using the
Reassign Work button) , then approved the change to push it to the project
plan.

Then I checked the project plan, and the task now has both resources names.
It did not replace one resource with the other, it appended the new resource
name.

I could swear that I tested this before and it worked fine.

Any explanation?

Thanks

 

[Dale Howard [MVP]]

LisaD --

If the original resource already did some work on the task, the system
assigns only the uncompleted work to the new resource, and retains the
original resource for historical purposes. Does this explain what happened?
Let us know.

 

[LisaD]

Dale,
Yes, some did have a % complete >0, however I just tried it on a 0% complete
task, and it still appended the name. And it is still in my My Tasks list.
I saved and republished the project, and the task still shows in my My Tasks
list.

Another interesting fact is that if you look at the Resource Usage, it shows
1 hr for the old resource, and 7 hours for the new resource for the same task.

Any ideas?

 

[Dale Howard [MVP]]

LisaD --

Try this:

1. Open the Microsoft Project plan.
2. Select one of the tasks in question.
3. Click Window - Split.
4. Right-click in the bottom pane (Task Form) and select the Resource Work
details from the shortcut menu.

In the Actual Work column for the resource with 1 hour of Work, does it also
show 1 hour of Actual Work? Check each of the tasks in question and tet us
know what you find. Also, what is your Service Pack level for both
Microsoft Project and Project Server 2007?

 

[LisaD]

Dale,
Our server was down for a couple days, so I just got back to this today.

The tasks with 0% complete have nothing in the Actual work column.

The one task with a % complete shows 30h in the Act. Work, and the rest in
remaining work for the new resource.

Also, we do not have any Service Packs installed. Only the hotfix from 4/29.

\lisa

 

[Dale Howard [MVP]]

LisaD --

The fact that your organization has not installed SP1 is problematic. I'm
not convinced your particular issue is due to a lack of SP1, but we strongly
recommend that you keep your Project Server 2007, WSS 3.0, and Project
Professional 2007 clients updated with the latest Service Pack. As of
yesterday, Microsoft also released a new Infrastructure Update for the
Project Server system. I would strongly encourage your organization to
update to at least SP1 as soon as possible. Beyond this, I have no other
ideas on how to solve the problem. Let us know if you continue to have the
problem after updating to SP1.

 

[LisaD]

Dale,
OK, I'll have my administrator load it.

We were going to a couple months ago, but then I read several entries that
SP1 introduced a few problems, so we didn't install it.

I'll let you know what happens.

Thank you again for your support. I would be totally lost without the help
from this site!

\lisa

 

[Dale Howard [MVP]]

LisaD --

You are more than welcome for the help, my friend!