All ideas
Sort by:
Trending
Status:
Showing 9098
1
VOTE
Integration of company's proprietary AI engine with Aha!
What is the challenge? User can only use default AI engine. Due to company's cybersecurity polices, we cannot enable AI related features. What is the impact? By integrating company own AI engine, the system will benefit from enhanced data security...
0
Unlikely to implement
1
VOTE
Idea portal terminology - identify when fields will display
What is the challenge? As users are customizing terminology within a portal it is not always clear when fields will display. We should provide clarity to simplify setup. Example - The fields below only display for submit only portals: Idea submitt...
0
Future consideration
1
VOTE
AI text editor in Idea's portal
What is the challenge? We use the idea's portal to collect problems and opportunities from our stakeholders. However, we often get low quality items or they are written as feature requests. What is the impact? It costs us all a lot of time to proc...
0
Future consideration
2
VOTE
In Ideas portal, flexibility to provide conditional logic wherein dependency exists with an Epic/feature. We are using Ideas for leveraging Dependencies.
What is the challenge? Users create ideas, without there is a proper dependency What is the impact? Data discrepancies, because users omit to include dependencies to other records Describe your idea Allow conditional logic, to make mandatory depen...
1
Already exists
2
VOTE
Epic/Feature boards using custom fields than versions
What is the challenge? Today we are not using Aha! out of box Releases and using a custom field for Release at Enterprise wide. So existing Aha! boards is forcing us to create versions at workspace but ideally we would like to use our custom field...
0
Future consideration
2
VOTE
When cloning, please provide ability to clear values in custom fields before saving in Domain Epics/Epics
What is the challenge? User clone records, without cleaning the existing data that is not applicable for the new record. What is the impact? Data consistency and re-work Describe your idea Have an option, when cloning to reset all the other attrib...
0
Future consideration
20
VOTE
Apply workspace templates to lines
Often settings like layouts, terminology, and navigation for parent lines may be purposefully different than workspaces. It would be helpful to drive standards for lines by allowing templates to be applied at those hierarchy levels. A few examples...
1
Future consideration
50
VOTE
Make admin access multi-level by organization/product line
We have multiple organizations/Business Units/Groups with their own product line in the hierarchy. We would like to be able to make them admin of just that area so that they can make the customizations they need without negatively impacting produc...
7
Future consideration
10
VOTE
Allow embedding existing whiteboards in records
It is possible to create a new whiteboard on the fly in an Aha! records, but there are times when I have already created a whiteboard I'd like to embed in a record. I can link it as a related item, but I cannot embed it directly. It would be great...
0
Future consideration
2
VOTE
Keep formatting from a Jira table
What is the challenge? The Jira integration does not currently support the table markdown syntax What is the impact? The result is a formatting issues when a record including a table within the description is synced to Aha! via the integration Des...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved