Capacity planning

Currently, the capacity report only shows monthly capacity by team or individual, but that's about it. To keep capacity planning centralized in Aha and not require export of Epic data to do other aspects of planning, I'd like to see the following:...

The individual capacity report only allows for viewing individual capacity in monthly buckets. It would be very useful to allow for configuring the time bucket (weekly/bi-weekly) to better match agile sprint planning (which for my purpose is in 2-...

I would like to be able to create a list report that shows all features with a remaining effort greater than 0. Currently, the Feature original estimate and the Feature remaining effort fields are not included in those allowed to be included in so...

A team will have a defined cost that is applicable for the calendar year. When putting together a multi-year plan, there needs to be a way to account for factors that will cause the team's cost to increase (e.g. inflation). There needs to be an ab...

I would like to limit the number of visible months in the Capacity Planning Detail view for any of my initiatives. See source issue: https://support.aha.io/hc/en-us/requests/499309

Often there are multiple folks working on a feature and even at a requirement/user story level, there could be multiple folks working. The ability to roll the combined efforts from 'to-do' to requirement and then to the feature (and include in the...

I use named ranges for adding t-shirt size estimates to my epics. I want to roll these estimates up across epics to the associated initiative so I can easily understand the effort and costs of the full initiative. This roll-up works for other sce...

Who would benefit? Teams using capacity planning for teams, planning with named ranges (e.g. t-shirt sizes) What impact would it make? Today, I am only able to report on the specific estimate associated with a record, not the named range value tha...

Who would benefit? Situation: I am using the best estimate on an epic. The epic has 2 child features with no estimates. My epic is set to calculate detailed estimate from child features Result: The epic shows the detailed estimate as Σ0 and not bl...

Right now, when you add a new scenario (even if it is just a test scenario), all users will be defaulted to that new scenario. We will have dozens of people using the tool, so the inability to get them to all set their own defaults to our standard...