What is the challenge? Do not want to see merged ideas on the idea board What is the impact? Shows ideas that have been merged into a parent when there is no desire to see them Describe your idea Allow the ability to filter merged id...

What is the challenge? We need to be able to pull the information from Native Theme field in the proxy votes as part of our insights tracking. There is a gap in our feature development roadmap development that would benefit our organization. The...

What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...

What is the challenge? Currently, a field cannot be required based on the value of another field. A few example use cases: If field A is selecting a Category from a dropdown menu: "User Experience", "Performance", or "Security," then field B w...

What is the challenge? We've recently added 'time in status' functionality to our reporting system. It would be useful to be able to visualize something like: "average amount of time features have spent in a given status by workspace." it could ma...

What is the challenge? There are teams who only use Epics in their workspaces, but the date range of Releases can only be calculated from Features. Moreover, there are no automation rules or integration mapping options to automatically update the ...

Epic, feature and initiative layouts allow you to require certain inputs when these records are created in the platform. But if they are promoted from an ideas, portal, individuals are able to bypass the completion of these 'required' fields.

For instance to indicate which budget holder / budget code a user is linked to.

When using master releases, it is not possible to select the release template for the sub-releases to be created. Which means the workflow to date looks like this: Create a master release Resist the temptation to select the products in the produc...

Generally Aha! is not intended for the storage of PHI, but some healthcare companies need their tools to be HIPAA compliant.