question Parent Project Task not updating State = Closed Complete when all child tasks are 100% complete. in SPM forum

Parent Project Task not updating State = Closed Complete when all child tasks are 100% complete.

WayneH490346913 — Fri, 23 Aug 2024 14:04:56 GMT

I am troubleshooting an issue where the parent project task state is not updating to a state of closed complete when the percent complete equals 100% and all child project tasks are 100% complete and in a state of closed complete. Please see attached screenshot. Based on my testing I have found that the parent task state DOES update correctly when the child tasks are set to one of the following: Pending, Open, Work in Progress and On Hold. But the parent state task does NOT correctly update when the child tasks are set to one of the following: Closed Complete, Closed Incomplete or Closed Skipped.

I'd welcome any insights as to what might be causing this.

Thank you - Wayne

Re: Parent Project Task not updating State = Closed Complete when all child tasks are 100% complete.

Community Alums — Mon, 26 Aug 2024 09:24:25 GMT

Dear @away ,

Please check what is the Top project for your project tasks. This is the only possible reason , Sometimes when you create tasks from workflow , Top project for the tasks will not be the Parent project.

please review parent and top project fields on the project tasks

Re: Parent Project Task not updating State = Closed Complete when all child tasks are 100% complete.

WayneH490346913 — Mon, 26 Aug 2024 11:00:58 GMT

Thank you for your reply Zeeshan. The top top task for project task that doesn't update the "State" is the parent project record so PRJTASK0221471 top task = PRJ0096590. There are 17 total tasks for this project, the task that is not updating the "State" is the only one that has child tasks. I have also checked for dependencies, in fact none of the tasks has any dependencies. I have also reviewed all the business rules that impact the task "State" and "% Complete" and I don't see anything that might explain this issue.

Re: Parent Project Task not updating State = Closed Complete when all child tasks are 100% complete.

Community Alums — Mon, 26 Aug 2024 11:31:45 GMT

Dear @away ,

since you have custom on hold state added, you must look onto the dictionary override of State field on planned_task table,

Re: Parent Project Task not updating State = Closed Complete when all child tasks are 100% complete.

Community Alums — Mon, 26 Aug 2024 11:42:37 GMT

you may need to do , your on hold state value 11 as pending state in attributes

Re: Parent Project Task not updating State = Closed Complete when all child tasks are 100% complete.

WayneH490346913 — Mon, 26 Aug 2024 12:22:30 GMT

I added 11 to the attributes as you suggested, then went back to the project record and changed all the child project tasks "State" to WIP, the parent project task then updated the "State" to WIP, I then updated the "State" for the child project tasks back to Closed Complete, but the parent task "State" remained at WIP, please see screenshot. I also did some additional testing and found that whatever "State" you place the child tasks in, the parent task will update to that "State" but when you change the child project tasks to any of the Closed "States", the parent doesn't update but just retains the last non-closed "State" the child project tasks were set at.

Re: Parent Project Task not updating State = Closed Complete when all child tasks are 100% complete.

Community Alums — Mon, 26 Aug 2024 12:56:28 GMT

probably last input from my side.

if this project is imported project ? does this happen to projects created from template or manually created project as well.

It works perfectly fine OOB without on hold state. Give it last try by creating project manually

Re: Parent Project Task not updating State = Closed Complete when all child tasks are 100% complete.

WayneH490346913 — Mon, 26 Aug 2024 13:24:07 GMT

The project was not created via import, it was manually created via the related link "create project" from Demand.

What I am going to try next is create a new project, add tasks, plus a task with child tasks to replicate this project record to see if I can replicate the issue in a net new project record. If not, then it may be something specific to the project record with the issue.

Thank you for all your help.