PWA Gremlins

M

Mark Byington

I have a PM who has a General Maintenance Project for his group that he
copies to a new one when the year changes. With the new one, he then only
keeps in-progress or not started tasks and deletes all others before
publishing.

In the old one, he completes all incomplete tasks, and changes all resources
from 'committed' to 'proposed' and republishes.

Eventhough the resource has no visible tasks in their timesheet, when they
update their tasks in "this year's" maintenance project, the PM often finds
tasks from 'last year' maintenance project to be updated on the update center
page. He rejects them.

How can this happen? How can I stop it?
 
D

Dale Howard [MVP]

Mark --

The biggest problem, I believe, is the process that your PM is using. I
would strongly recommend the "cease and desist" this process and implement a
new one. The new process would be:

1. Save the General Maintenance Project as an .mpp file for analysis.
2. Project Server administrator deletes the old General Maintenance
Project.
3. PM creates a new General Maintenance Project (no copying; create it from
scratch or from a template).
4. Publish the new project.

I'm sure that this is not what he wants to hear, but his process is flawed,
which I suspect is the source of his problems. Hope this helps.
 
M

Mark Byington

Thanks for the advice, Dale.

However, we still have the problem as described to resolve. I noticed in
the indicator column on Project Pro an icon that states: "There has not yet
been a response to the progress information request for this task."

I suspect this may have something to do with it. How is it generated? Can
we make it go away?
 
Top