Follow
Projected Duration Does Not Match Planned Duration

Problem

The Projected Duration of a Task/Issue has gone to 0 and does not match the Planned Duration. 

This is caused by the Projected Start Date matching the Projected Completion Date.

Solution

There are many factors that can cause the Projected Start and Completion dates to match. This problem is largely tied to the allocation against the Task or Issue in question.

In most cases, depending on the duration type and task constraints in use, the allocation should extend the Projected Completion Date out much further than expected. However, in some cases based on the way duration type and task constraint are configured, it is possible that this will instead zero out.

Here are the best things to check in those cases with links to their supporting articles:

If the projected completion date, task constraint, or duration type are working as expected, contact support for more in-depth troubleshooting. 

This article last updated on 2018-05-10 18:46:37 UTC