Best Practice for Stopping/Pausing a Project

[melissahill]

Ok - I've read through community posts on putting a project "on hold" with a custom state.  To me, that seems really tricky because you would then need to control any duration, status reports, etc based on when the project was placed "on hold".  I am wondering what the best practice is, or what others have done to handle situations where projects that are currently underway have work stopped.  

I can see that we would want the project itself to NOT require any more status updates, time entry, etc.  

I could also see that we would not necessarily start the work again at a set point in time.  It may need to be evaluated against other demands to determine what gets worked on next, when resources/funding/etc become available.

It seems really strange to me that nothing exists OOB for this type of action.  The closest thing I have found is the "Move Project" UI Action.  

Any thoughts??

[Miguel Donayre]

I wish I can provide you with a good solution, but I can't. Everything I have seen all requires customization. 

There is an Idea on the community for this same use case. To add a hold state for a project. I the idea gets enough votes it will be looked at to be added in a future release. I have already voted it up. - https://community.servicenow.com/community?id=view_idea&sysparm_idea_id=bce469cbdb6d445023f4a345ca96...

[Dhiren Aghera]

There is no OOTB way to put a Project on-hold as Miguel mentioned. What we have done in our Org to achieve is we have added a custom field "Sub-State" to put a project on-hold and also date fields to capture when the project was on-hold and off-hold. This way we also know the duration for which the project was on-hold and also helps to exact the Project duration.

Also have added control that a closed complete project cannot be in the on-hold state. 

Hope this helps.