Rejected Task updates

[AmWall]

I am using Project Server 2007 pre-SP1.
We have a large number of tasks that are showing up in the Tasks results
indicating they are rejected for invalid data. The PM's have created Manage
Rules that Approve all Task updates.

On another note we are having problems with PMs that are only Saving changes
to the project plan not Publishing the changes then other PMs opening the
same Project updating the plan Saving and not Publishing. I think this is
creating problems with the integrity of the Project and that the changes
should be Published. The reasoning behind not publishing is that they do not
want the Resources receiving email notifications constantly regarding task
updates.

Would this behavior have something to do with the first problem?

How do we fix the rejected, or find out what is rejecting them?

Thanks
Margaret

 

[Dale Howard [MVP]]

AmWall --

Your second paragraph probably reveals the source of the problem in the
first paragraph. You must absolutely teach your PMs to publish the latest
project changes after EVERY session of updates to EVERY project they manage.
There is really no excuse for this. Using Rules is NOT an effective
workaround in my opinion, and I think you should try to discourage them from
using Rules.

Think about what might be the source of the problem. The TM submits a task
update on task information that is old, outdates, and invalid. What is
Project Server 2007 supposed to do in that situation? I'm sure that is why
the task updates are being rejected due to invalid data.

Regarding the constant bombardment of e-mails from Project Server 2007, I
have stated again and again in this newsgroup that each team member should
DESELECT the "My project tasks are modified" option on the the Manage My
Alerts and Reminders page in PWA. This will stop what seems like "spam"
from Project Server 2007, and will force the system to only send e-mail
messages when the team member gets assigned to a new task in an existing or
new project.

So, the first step in the solution is for all PMs to publish every project
they manage, if they have not done so after the last round of updates.
Then, perhaps your TMs can submit updates that won't get rejected. Hope
this helps.

 

[AmWall]

Dale,
Again, I thank you for your timely response. I knew that was the problem.
Do you have a source for Best Practices for Project Server that you recommend?

 

[Dale Howard [MVP]]

AmWall --

Our "Managing Enterprise Projects..." book is filled with notes, tips, best
practices, and warnings about using Project Server 2007. You can purchase
it at:

http://www.projectserverbooks.com

Hope this helps.