Preserve requirement roll-up estimates in feature-level capacity reports

What is the challenge?

• Capacity reports at the feature level do not retain requirement-level estimates when a feature is configured to use rolled-up requirement estimates.

• This forces teams to use separate feature and requirement-level views to plan work.

What is the impact?

• Capacity planning can underrepresent or misallocate work at the feature level, even though the feature’s rolled-up estimate is correct.

• Teams cannot rely on one capacity view to understand individual and team workload across their planned features.

Describe your idea.

• When a parent record uses estimates rolled up from child records, preserve the child records’ estimates in the parent-record capacity view.

• Support this alongside features with estimates entered directly, so both planning approaches can be represented accurately in the same capacity report.