All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5836
13
VOTE
Seamless Sync for Epics and Features Between Aha! and ADO when changing types
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...
1
Future consideration
5
VOTE
Gainsight integration for populating interview participants
What is the challenge? Gainsight has information about end users and their usage data, which could be valuable to have in real-time. What is the impact? A more powerful participant list, leading to more product insights. Describe your idea An inte...
0
Future consideration
13
VOTE
Sort the list of release templates to appear in alphabetical order or set manually
What is the challenge? Large lists of release templates can be difficult to manage and sort. Not having a set list and being able to sort the order alphabetically or manually increases the time it takes to find a release template. This is also the...
0
Future consideration
30
VOTE
4
VOTE
Improve Attachment Management for Ideas / Features / Epics
What is the challenge? There are multiple ways to add attachments to ideas/features/epics. The only standard attachment field is on the description. When creating work requests, must move attachment to description to carry over. When integrating w...
1
Future consideration
5
VOTE
Add email address when searching for Aha! user
What is the challenge? We have several employees with the same name, which makes changing the Idea Creator to the correct user challenging when we have no way of differentiating who is who. We need to update the created by field because when users...
0
Future consideration
91
VOTE
19
VOTE
Better automations management and reporting
Who would benefit? Workspace admin & users What impact would it make? improve reliability and documentation How would it work? Allow the extraction of metadata detailing existing automations By providing an endpoint or similar option to output...
2
Future consideration
76
VOTE
Control which personas & competitors should be inherited and which not
At the moment all personas & competitors are inherited from the levels above even if some do not apply. In order to avoid duplication by defining the same persona/competitor over and over at the product level it would be much better if persona...
4
Future consideration
6
VOTE
Create a new field type to make establishing relationships to records more consistent
What is the challenge? Today teams can create any relationship between any record through record links. As standards are established some teams would like the ability to ensure specific relationships are set between set record types. What is the i...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved