Planner Premium <% complete> calculation is strange

Copper Contributor


I encountered a strange behavior of the <% complete> field in the premium planner when you change the <duration> and/or <effort> fields after you started a task, e.g.

  1. Set <start date>=today, <duration>=20 days, <effort>=40hours, <% complete>=50%
  2. Then change <duration> and <effort> to accommodate for unexpected delay/scope extension

Doing this, you will end up with a completely broken <% complete> value as shown in the image below.

It seems that the <duration> field is somehow integrated in the calculation of <% complete>, which I feel is odd.

Happy to get some feedback




0 Replies