My company would find it useful to have Burn *Up* charts that show how the effort completed is tracking against the scope of a release / master feature / feature
For more on the requirements for a Burn Up chart and why it is more useful than a Burn Down chart, see here...
http://www.clariostechnology.com/productivity/blog/burnupvsburndownchart
Introducing burnup charts to track the impact of scope creep
See the impact of scope changes on your delivery plans. Use the new burnup chart in Aha! Teamwork and Aha! Develop to forecast when work will actually be completed.
https://www.aha.io/blog/introducing-the-burnup-chart-to-track-the-impact-of-scope-creep
Our new leadership team prefers Feature level burnup reporting over burndowns. This will force me to obtain this through either TFS or Excel meaning less time that our users will spend in Aha. Hoping that this change is implemented in the near future.
Although I submitted this in the "Releases" area, it is equally useful for Master Features and Features reporting as well (possibly even more useful)