RELATED IDEAS
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.
© 2026 Aha! Labs Inc.•All rights reserved
Yes, this would be more than just helpful, and would prevent errors in capacity planning.
In our implementation, we use Initial Estimates at the initiative and Epic level, and Detailed Estimates at the Feature and Requirement level.
So, we would have 2 instances:
The feature does not need breaking down into requirements, therefore the feature would have a manually entered estimate
The feature does need breaking down into Requirements, each with an estimate. Therefore the Feature would be set to roll up its Detailed Estimate from the Requirements
In all instances, the Epics and Initiatives that sit above would be configured to roll-up their Detailed Estimates from next level below, i.e. Initiatives->Epics->Features->Requirements
The capacity report should respect this whole chain.