All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5656
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
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
Ability to add text above a table or callout box at the top of a note
What is the challenge? When a table or callout box is at the top of a note, I'm no longer able to add text or anything else above it, nor can I move the table or callout box down in order to do so. I've also noticed similar behavior when the first...
1
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
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
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
11
VOTE
Include ideas in both Research Tab and Related Tab
Having ideas included in the list of other research assets makes sense when I want to view all of the work that went into defining an initiative or feature. However, there is also a need to see all related items in a single location. For this, I w...
2
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
© 2025 Aha! Labs Inc.•All rights reserved