We'd like to estimate and plan releases based on velocity (rate of story point completion) rather than capacity (static value).
We're aware Aha! calculates velocity based on points completion over time for reporting, but it's not being incorporated in release planning. Rather than hard-coding capacity for each release, you could have an option to calculate capacity based on measured velocity for the product (and accept some starting estimated velocity).
Looking forward in time, it's often possible to anticipate increases or decreases in velocity due to hiring or attrition and other factors, so it would be useful to apply adjustment factors onto the current velocity for roadmapping.
This approach allows product managers to project future progress against key initiatives without unnecessary tedious calculation, or delving into product dev team organization and productivity.