Capacity planning

What is the challenge? searching for work allocated to your team currently not possible, only the assigned persons capacity team What is the impact? Means teams cannot easily create workflows or search boards for features where they have been allo...

What is the challenge? When prioritizing features using capacity per release, x-team capacity isn't taken into account by aha! What is the impact? Difficult to allocate features to releases where they may have varying team capacity requirements. D...

When viewing the capacity report, if a team has no capacity to work on initiatives, it would be great to have a visual indicator that they have 0 hours available for initiatives. Right now when you view it, it looks like they're not being used at ...

Dear aha, could you please decouple the settings of actual effort field from initial and detailed estimate? Scenario I am having> teams handle estimations differently on requirement level in JIRA (stories, bugs, spikes..) they do estimations ei...

We would like the ability to add a few fields to the detail view to help decide which Features/Epics we need to cut, renegotiate, or move to other teams. We have two custom fields that would be helpful to add here (Feature Priority and PI - Planni...

Our business stakeholders, rightfully so, need to understand the level of effort involved in the various items on our roadmaps. At the most basic level, this equates to showing them the number of developers involved in a given item (epic/feature),...

We need the ability to filter/sort a list report to highlight Features that do not yet have an Initial Sizing. This is important as we are looking to "draw the line" as to which features can be brought into PI Planning.

We need the ability for the report to pull the estimate from a feature AND if there are multiple time estmates on the requirements tab , the aggregate of that time needs to overwrite the time range on the overview tab on the feature

We have different teams that work around the clock in the each release. I need to be able to track per release the capacity so I can visualize each team individually and as a whole.

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.