My votes: Application

Part of our research ops process includes live, in-person, sessions with single and multiple users which we record and have transcribed. However, bringing those conversations into an Aha! Empathy Session is a BIG pain in that we have to copy/paste...

The desired use case to see supported is as follows: 1. Director of User Experience or Product Management creates (at the product line level) all possible personas for a product line.2. Each Product Owner then removes/hides (at the product level) ...

We love Aha! for it's flexibility. However, it would be great to configure something platform wide (our platform). We would love to be able to have warnings if the user tries to move a feature from one product to another. This happens to us (accid...

Mockup provides a powerful method for idea contributors to communicate their ideas. However the mockup tool is only available to users with contributor or greater permission. But contributor is too permissive, allowing user to create features, str...

This is a need for us in order to get feedback on our product. We are not interested in a shared feedback widget, but interested in individual feedback from every single user. We don't want to 'spam' our users/customers with feedback from other us...

Similar to the ability to create Ideas via email, we would love the ability to create Features via email submission. Our ideal workflow is to have support issues and bugs submitted into Aha! and this would simplify things so that users aren't send...

Simple one, use Gravatar instead of default image for your users if they haven't added a profile pic. https://en.gravatar.com/site/implement/images/

It would be great to have an option when exporting a single feature to have it include the comments. I state as an option because there are instances when the comments are not necessary but for others it is quite necessary.

As the release date changes, it's hard to recreate history to figure out what the original date was along with interim dates and the final release date. It's also hard to remember the reasons for a change when it's several months later. I'd like a...

We have an Epic (Initiative) - Feature - Requirement breakdown structure. It would be very useful to be able to visualize the dependencies using these existing relations instead of requiring to add separate link specifically for the dependancy map.