How Can I Stop A Project From Closing When All Project Tasks Are Closed

[Casey23]

Hello,

I'm wondering if anyone can tell me what controls project closure once all project tasks are closed and whether or not this behavior can be changed? We are attempting to solve two issues right now:

Issue 1: Don't allow people to close a project until they have addressed all open resource plans

Issue 2: Don't allow people to close a project unless the phase is closing

For issue 1, I updated our "Close" UI Action so that it shows a message if someone tries to close a project using the proper method, but didn't address all of the resource plans. The issue though is that if someone completes all of the project tasks, the project state is set to closed and the message is never shown. This results in people just ignoring any resource plans that are still left out there.

For issue 2, if the PM doesn't have tasks setup for activities after the executing phase, someone who is an analyst for example, could close the last remaining task on the project which sets the state to closed, even though the PM and possibly others still have active tasks (not project tasks but just stating that there are usually post go live activities with any project) that need to be completed like dealing with resource plans. Users who aren't the PM shouldn't have control over whether or not the project is closed.

TIA

[Mark Manders]

Check on the script includes behing this BR: "Process State Change" 

[Mani A]

Issue 1 : Modify your UI action to check any open resource plans available or not for the project 

Adjust existing/create a new BR to check if open resource plans available and if yes stop changing state to close 

Issue 2; create/update BR that checks the project phase before allowing a state change to "Closed."

Or in same above UI action check if user has  PM role or not to close the state