Project Task % Complete: how is it really calculated, and can it be changed?

Nora Wainwright
Giga Contributor

Per the Planned Task documentation, percent complete is described as being calculated based on planned effort and actual effort for an individual planned task. And as far as I have found, there is nothing documented for how percent complete rolls up to the parent based on subtasks.

Here is what we've experienced, at least in Jakarta:

  • On an individual task, neither planned nor actual effort have any effect on percent complete. It doesn't seem to be calculated by anything other than what the user enters.
  • When rolling up to a parent task, percent complete appears to be a function of total planned duration of all subtasks. For example, if one subtask is 100% complete and 10 days and a planned duration of 10 days, and another task is 0% complete with a planned duration of 10 days, the parent task calculates 50% complete.

Is this intended, and is there any documentation out there that I'm missing that explains this?

Also, is there any way to modify the rollup calculation, so it uses effort instead of duration?

1 ACCEPTED SOLUTION

Balaji39
ServiceNow Employee
ServiceNow Employee

Hi Nora and Roger,

We acknowledge the problem with the milestones not being factored in for the % Complete calculation. We are working on fixing the same.

Currently, the % Complete of the parent task is derived using the Planned duration as observed and we do not factor the planned or actual effort. In case of a sub-task, the % Complete is editable and require the user to input the value manually.

I will work with the documentation team to have this documented.

Thanks,
Balaji

View solution in original post

5 REPLIES 5

Was this Fixed  ? Any documentations KE KEDB etc available ?