Can I stop a project from showing in PWA "assign myself to a task

[Jeff_Sells]

Any basic input that I can receive would be appreciated.
Regards,
Jeff

 

[Dale Howard [MVP]]

Jeff --

If using the "Assign myself to a task" feature is problematic, it would
probably be best if your Project Server administrator disabled this feature
entirely, or at least disabled it for members of the Team Members group. I
believe the permission is called New Task Assignment and if you want to
disable it for team members, your Project Server administrator should set
this permission to Not Allowed (neither Allow or Deny is checked) in the
Global Permissions grid in the Team Members group. If you have a single
user abusing this feature, your PS admin could edit the individual user's
account in PWA to disable this permission. Hope this helps.

 

[Jeff_Sells]

Hello Dale,

Thanks for the response.

By "problematic" do you mean it is "buggy" or that it is not a good business
practice to allow personnel to assign themself to existing project task?

It appears that only .published projects appear in the list.
I guess another way for me to look at this is how do I close a project once
it is complete. (? change it from .published to .archieve ?) The only thing
that I have found so far is to delete it from the project server - which is
not what I want.

Any additional input that you can provide would be greatly appreciated.
Regards,
Jeff

 

[Dale Howard [MVP]]

Jeff --

I used the word "problematic" as in "the use of this feature is causing
problems in your project management environment." Obviously this feature is
causing problems for someone in your organization, or you would not have
sent your original post about the situation. Right?

If you want to close a project once it is complete, there are two things you
could do in your organization:

1. Ask your Project Server administrator to create a custom enterprise
Project outline code called something like Status. In this outline code,
include status-related items such as In Planning, Production, On Hold,
Cancelled, and Closed. Once he/she has created this outline code, ever
project manager would need to open every current project, click Project -
Project Information, and then select a value from the list that indicates
the current status of their project. Once done, they will also need to
click Collaborate - Publish - All Information to "push" this information to
PWA.

2. When you close a project that is complete, you will set the Status value
to Closed using the steps in #1 above. You would also click Tools - Build
Team from Enterprise and set the Booking type value for each team member to
Proposed. Once done, you will need to click Collaborate - Publish - All
Information to "push" these changes to PWA. Doing so will remove the tasks
from each team member's timesheet in PWA for that project.

Just some thoughts. Perhaps others have an idea, too. Hope this helps.

 

[Patrick]

We use the custom status outline code as Dale recommends in Number 1 below.
However, instead of changing the resources to proposed, we wrote a sql
statement that runs daily looking for inactive and closed project statuses
and setting the assignments to be hid on the web (WASSN REMOVED BY RESOURCE).
That way we can reopen or reactivate and just republish if necessary to see
the assignments again...

Just another alternative...