Hi,

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.

Set <start date>=today, <duration>=20 days, <effort>=40hours, <% complete>=50%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

Lasse

​Hi,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.Set <start date>=today, <duration>=20 days, <effort>=40hours, <% complete>=50%Then change <duration> and <effort> to accommodate for unexpected delay/scope extensionDoing 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 feedbackLasse   Read More

​<img src="https://techcommunity.microsoft.com/t5/image/serverpage/image-id/590617iDF2BA16A92779068/image-size/large?v=v2&px=999" title="Planner Premium calculation is strange” />