My ideas: Capacity planning

Our company needs the ability to track CapEx hours as well as utilize the story points on the features. It would be nice to have a way to track CapEx hours at the requirements level.

When a feature has "Use requirements estimates" enabled and there are no requirements added, a feature estimate can be entered. However, capacity planning does not update the following: 1) When the Progress field is based on remaining estimate, it...

Once a capacity plan has been built, it would make it easier to do what-if type comparisons if you could create a copy of a Scenario pre-populated with the estimates already in the initial scenario. This would let you change aspects of the capacit...

It would be valuable to be able to execution against a capacity plan. I envision that this would involved being able to snap a baseline once you're settled on a capacity model. Then as you make changes during execution in terms of timing of delive...

Currently, it's not possible to view the capacity report on the dashboard, only on presentations or a shared webpage. This is a major area of importance for us as we grow and update our procedures.

We use time-based capacity planning in Aha! Develop. Many of our features take less than an hour, e.g. 30 minutes. I would like to enter this as "30m" instead of "30min".

In the below screenshots, email address is a required field on the first screen, but not on the second. Email address shouldn't ever be required when creating a virtual user.

For me, it's difficult to use week numbers when trying to enter the number of hours I need to assign for a resource. My project plans use actual dates, not weeks, so I would rather use the week starting date. The way the capacity plan page current...

It would be helpful to be able to lock the status of items within the parking lot to ensure agile capacity planning for team. This would align any items on the active board to the correct planning stage, and eliminate room for error within the par...

We have multiple teams using Aha within a workspace. Some of these teams use Story points, other use time based estimates. While we can set the estimate type used per release within one workspace, we can't import story points into the Original Est...