Project state is closed complete but its sub-project is still in 'Work in Progress' state

_Yash24 · ‎03-09-2023

Hi All,

My Project State is 'Closed Complete' even though its 1 Sub-Projects state is 'Work In Progress'.

When sub-project state is 'Work In Progress' it shouldn't be in 'Closed Complete'.

What could be the reason here?

Also when I'm trying to change Sub-Project state manually from 'Work In Progress' to 'Close Complete', Its giving me 'Invalid Update' error.

This is happening only for one project.

Can someone please help me understand what could be the issue here?

BharathChintala · ‎03-21-2023

@_Yash24 most common cause for this is customizing the OOB script include and adding custom states to project table.

Can you confirm you did any of these?

If my inputs have helped with your question, please mark my answer as accepted solution, and give a thumb up.
Bharath Chintala

_Yash24 · ‎03-23-2023

Hi @BharathChintala,

Thank you for reply, Yes there was customization done on pm_project with different state values and corrected the state and it resolves the issue.

Rajesh_Singh · ‎03-21-2023

@_Yash24

It seems there might be a discrepancy in the workflow or a configuration issue causing this behavior. Here are a few possible reasons and steps to troubleshoot the issue:

Workflow issue: Verify if there's any custom workflow set up for project or sub-project states. If there is, ensure it follows the correct logic to avoid such inconsistencies.
Business rule or script: Check if there are any business rules or scripts in place that might be interfering with the state updates or causing the 'Invalid Update' error. You may need to correct or disable these scripts to resolve the issue.
Mandatory fields: When manually changing the state of a sub-project, ensure all mandatory fields have been filled in. It's possible that an incomplete form is preventing you from updating the state.
Data inconsistency: It's possible that the specific project or sub-project in question has some data inconsistency or corruption that is causing this issue. In this case, you may need to involve your ServiceNow administrator to investigate and correct the issue at the database level.
User permissions: Ensure you have the necessary roles and permissions to change the sub-project state. If not, you may need to ask your ServiceNow administrator to grant you the appropriate access.

If you found my response helpful or applicable, please consider marking it as correct or helpful to assist others who may be seeking the same information.

---------------
Regards,
Rajesh Singh

_Yash24 · ‎03-23-2023

Hi @Rajesh_Singh ,

Thank you for reply, Yes there was customization done on pm_project with different state values and corrected the state and it resolves the issue.