Capacity planning - initial and detailed estimates behaviour in capacity report

When a record is assigned to a user and you enter a detailed estimate, the full estimate is automatically attributed to that user — even when the detailed estimate is actually based on estimates entered on child records that are assigned to multiple, different people.

This means a team capacity planning report that is using rolled up detailed estimates will likely show an incorrect allocation of estimates to one person, instead of multiple people who may be on several different teams.

The current workaround is to review estimates only at the lower level where the detailed estimates are assigned to the correct individuals:

• Working at a lower level is possible but not ideal. It is valuable to see, from a higher level, how work has been estimated — whether via a single initial estimate or by rolling up more detailed estimates from lower level child records.

Unhelpful estimates that are allocated to the wrong people. The workaround can be confusing or unhelpful.

Add an option in the capacity planning for teams report to ignore the assignee on the selected record. When this option is enabled, records that use initial estimates continue to rely on the team-based estimate, while records with detailed estimates that roll up from child records use the child records’ detailed allocations instead of the parent record’s assignee.

Example:

• An epic has an initial team-based estimate and a detailed estimate that is calculated by rolling up detailed estimates from several child features. The features are assigned to different users who belong to various teams.

• If you choose to ignore the assignee on the epic, the detailed estimate allocations at the feature level are used in the capacity report, rather than assigning 100% of the detailed estimate to the user the epic is assigned to.