All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5655
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
1
VOTE
Allow Aha! user to view portal user org name in portal
What is the challenge? When viewing ideas and comments in the portal I can't see which org they are from. I can see this in Aha!, but it's easier (and somehow more fun / more satisfying) to view ideas and comments in the portal except for this one...
0
Future consideration
1
VOTE
Show more details in history when integrations/automations/extensions change data
There are many times when an integration, automation, or Develop extension will modify data on a record, but it's not always obvious how or why that data was modified: For integrations, all changes will be done as the integration user. It might no...
0
Future consideration
1
VOTE
Improve user experience of Idea Category type custom field
We promote Ideas to Epics and automatically populate the Idea Categories field into an Epic field, which calls from the idea categories of our product line. When we try to modify or add categories using the Epic field, we are encountering some iss...
0
Future consideration
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
5
VOTE
Schedule when a document will be published to a KB
What is the challenge? You need to manually publish Knowledge base updates. What is the impact? If you are planning a release or something similar you may want to publish the updates to go out automatically. Describe your idea Add ability to sched...
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
68
VOTE
Handle multiple FixVersions in JIRA
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
15
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved