Completed Tasks Still Getting Alerts

[BAndrews]

Is it "by design" that even though tasks are completed that project server
is sending out notifications that they are due?

I am trying to minimize the amount of noise that PS is producing for our
team and this doesn't help.

 

[Gary L. Chefetz \(MVP\)]

No. It would indicate that the task or assignment was not properly or fully
statused as complete. This could happen, lets say, if a PM were to mark a
task complete without closing out an assignment on the task.

--

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

-

 

[BAndrews]

Can you please define: Closing out an assignment?

 

[Gary L. Chefetz \(MVP\)]

B:

When you "publish" a task, "assignments" get created in the database. To
"close" an assignment, you must remove the remaining work for the particular
user/assignment and republish the assignment so that this is also reflected
in the web assignment tables.

--

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

-

 

[BAndrews]

OK,

There is no remaining work in project and I am pretty sure all the changed
assignments were published when we marked them all "complete". I just tried
to publish new and changed assignments and nothing needed to be published.

I understand that i can republish assignments, but is this necessary because
something is wrong here or is this by design? If this is by design can you
clarify the process and why this does not occur when publishing changed
assignments?

Thanks!

 

[Brian K - Project MVP]

Is it "by design" that even though tasks are completed that project
server is sending out notifications that they are due?

I am trying to minimize the amount of noise that PS is producing for
our team and this doesn't help.

I seem to remember something like this getting fixed in Service Pack 1.

Are you in 2002 or 2003?

--
___
Brian K
Project MVP
http://www.projectified.com

Project Server Consultant
http://www.quantumpm.com

 

[Bryan Andrews]

2003 - How do you confirm what version you are running? (whether or not you
have installed sp1)?

Thanks!

 

[BAndrews]

No matter what i do (mark as complete and republish all assignments) the
users assignments still show in Project Web Access as incomplete with
remaining work.

Even though they have not updated actuals on any tasks... the only way i
could mark everything as complete on the project server side is to
"overwrite actuals".

Is this the only way to do this? Or is this the proper way to do this?
Thanks!

 

[Gary L. Chefetz \(MVP\)]

Bryan:

How are you updating remaining work before you republish? Certainly,
selecting overwrite actuals will affect the change you seek.

--

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

-

 

[BAndrews]

We had a project that was cancelled and i marked al tasks 100% complete. I
really did not want to change the actuals at this point as i wanted the
project to still accurately show how much work had been completed.

Also there were tasks that had no actuals entered by the users so i found
this strange that i needed to "overwrite actuals" for these tasks.

 

[Gary L. Chefetz \(MVP\)]

That's a simplistic approach, which accrues all planned work to the
resources. In this case, you must use Republish and select Overwrite actual
work to synchronize the web tables. The proper way to close an assignment is
to remove remaining work, as I stated in a previous post.

--

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

-

 

[Brian K - Project MVP]

No matter what i do (mark as complete and republish all assignments)
the users assignments still show in Project Web Access as incomplete
with remaining work.

Even though they have not updated actuals on any tasks... the only
way i could mark everything as complete on the project server side is
to "overwrite actuals".

Is this the only way to do this? Or is this the proper way to do this?
Thanks!

Wait a sec. Are you saying that the resources themselves have never
updated their timesheets but rather you entered the Actual Work for
them directly in Project Pro?

If this is the case then doing a republich and Overwriting IS the way
to have them marked as complete in PWA.

This is different problem then the one is sounded like you were talking
about.

--
___
Brian K
Project MVP
http://www.projectified.com

Project Server Consultant
http://www.quantumpm.com

 

[Brian K - Project MVP]

We had a project that was cancelled and i marked al tasks 100%
complete. I really did not want to change the actuals at this point
as i wanted the project to still accurately show how much work had
been completed.

Also there were tasks that had no actuals entered by the users so i
found this strange that i needed to "overwrite actuals" for these
tasks.

Marking them as 100% put actual work on them which is why you had to
overwrite the actuals.

Gary is 100% on this one. If this happens again do not just mark
everything complete as this will ADD actual work to every task that is
not already complete. Setting Remaining Work to 0 keeps the current
level of actual work and still ends the tasks. If you had done this you
would have only had to publish new and changed.

--
___
Brian K
Project MVP
http://www.projectified.com

Project Server Consultant
http://www.quantumpm.com

 

[BAndrews]

Gotcha. Thanks Gary and Brian.

Marking them as 100% put actual work on them which is why you had to
overwrite the actuals.

Gary is 100% on this one. If this happens again do not just mark
everything complete as this will ADD actual work to every task that is
not already complete. Setting Remaining Work to 0 keeps the current
level of actual work and still ends the tasks. If you had done this you
would have only had to publish new and changed.

--
___
Brian K
Project MVP
http://www.projectified.com

Project Server Consultant
http://www.quantumpm.com