Capacity reports should respect manually entered totals for named range scenarios

What is the challenge?

• Capacity reports do not respect manually entered totals for named range scenarios

  • 

• Instead, the reports fall back to using the initial_estimate field, which leads to miscalculations

• This is actually true for all scenarios, but it's especially visible when using named range scenarios

The estimate shows one value, but the capacity report shows something drastically reduced (often minutes instead of days).

What is the impact?

This creates confusion for teams and leadership, derails strategic planning conversations, and generates recurring escalations to support.

Describe your idea

Update the system so that capacity reports consistently respect the total field when it is manually entered in a capacity plan. Ensure that these totals flow correctly into reports, aligning what customers configure with what they see in reporting views.