apply rank opens a picker to let user decide which custom field to apply the rank value to , and that custom field needs to be the field in the mappings that provide update into target tooling (my case, its ADO, stack rank). I see multiple custom ...

We have a large client list and when a feature has been requested by a client, we associate the client to the feature. With a long list of clients, being able to sort the Alphabetically (ascending/descending) would make choosing the Clients far ea...

Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...

The ideal workflow for a SAFe team is as follows: Define work (workspaces and teams): product and engineering define the work to be done Prioritize work (backlog management): work is groomed and assigned to the prioritized backlog Plan PIs (progra...

I use the List Report screen to manage my entire pipeline of ideas where I can sort and filter to determine priority. Most importantly, I use this List view to consolidate Ideas by Customer to go over in meetings. While in this view, if a stakehol...

When prioritizing features, it would be nice to work on features that belong to one release. So being able to only select the features from a roadmap would be nice

I'd like to be able to map out a use case map using Whiteboards, and it would be helpful to include a "person" shape. It would also be good to have a "team" shape available

Aha! allows product managers to stay at the 40k foot level, while JIRA is used by our development team, which means it contains lots of small implementation details. If all the bugs and tasks being logged by my developers in JIRA reflect back into...

Ability to showcase Delivered Ideas externally to customers, like a banner or popup, on the home page with link(s) to more information.