Capacity planning

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...

When creating or changing a team, there is an option to manually set the teams capacity instead of having it calculated from #people*schedule. However, the manually set capacity is not reflected in the capacity report. The only way around this is ...

Hi there! love Aha! its an awesome tool, however we are having problems with timetracking, would it be possible to have something like Tempo in Jira? thanks and hope this makes it through!

My agile development team uses story points for estimation. Once work is in progress, I want my developers to log work in time. This helps me understand where their time is going, and to inform future estimates for planning.

When teams work across products we need the ability to rank items within their own list of items to support the planning processes.