Closed Complete Project Tasks showing as Active

[Nickels]

We have started using the projects application within ServiceNow and I have been looking into an issue that is being reported to me. We have 'My Work' reports setup on our homepages to show Active Assigned tasks for a user. They are finishing work on their project tasks and closing them in the status of Closed Complete. When they refresh their homepage some, not all, of these tasks will still appear. I went directly to the pm_project_task list and was also able to verify that the tasks are still showing as active. I actually have 219 project tasks that are currently closed complete but still active.

When I look at the Audit History list for one or any of these project tasks, I can see that the active flag was set to false when the status changed. I am not seeing where it was set back to true though so that it is still active.

I decided to look at the parent record of the PRJTASKs but I found one right away where the is a task was closed complete and the active flag is false. So now I am thinking that it is not directly tied to the parent record.

Does anyone know of a business rule that might be doing this? I am also wondering why I am not seeing the active flag changed back to true in the audit history but my prior question is the one I want to get resolved.

Thanks

-Chris

[Luis Franco]

Hi to all.

Just to say we have the same issue in our istanbul release. The planned task has all the dictionary overrides on the closed states atributes OOTB with 3;4;7 and that is not making the active correctly calculated.

Thanks,

Luis

[mikemorales]

Hi Nickels,

This has been related to PRB1202324. This is caused when:

"Using add task below in the planning console in a project that already has closed compete tasks can cause those closed tasks to become active=true again incorrectly."

To fix this issue, HI has recommended to go to your project preferences and set 'Enable firing off Business Rules on Save from Planning Console...' to 'true'.   Initial testing of this has indeed fixed the issue within our sub production instances.   However, I am still in need of more regression testing to ensure this does not cause any noticeable performance degradation.     Initially, I was unable to detect any, but a little more testing and I will end up moving this to production.

I hope this helps anyone that has had this issue in the past and you can now go back to allowing or filtering on Active tasks, like is intended

Thanks,

Mike

[tim2222]

I've reported this issue to 'hi' and been informed this is resolved in the Kingston release (so no immediate benefit to us).

We implemented the work-around, which is to enable business rules on the planning console. Subsequently we have found that at least the project task's description is getting deleted when manipulating the project via planning console. I have confirmed this behaviour in a developer instance of Jakarta and reported it to 'hi'.

Loss of data is a more severe issue than the original problem so we've undone the workaround and will seek an alternative fix from 'hi'.