Application
Sort by:
Trending
Status:
Will not implement
Showing 7871
1
VOTE
Automation: require field based custom field option
What is the challenge? During the lifecycle of an Epic, we have fields that when a certain option is selected, another field should be required. What is the impact? Data is not complete so reporting is incorrect. We have features that that when a ...
0
Future consideration
1
VOTE
Ability to abbreviate long text fields in reports
What is the challenge? There's no easy way to summarize long text fields in reports. What is the impact? I end up having to export reports to excel and email reports instead of use Aha. Describe your idea I'd like to use a formula to identify whet...
0
Future consideration
1
VOTE
1
VOTE
3
VOTE
Support a hyperlinked image in the text editor
What is the challenge? Instead of using plain text with a hyperlink on a published note, I want to be able to add a link to an embedded image on the note. It would make it look more graphically pleasing for the end users consuming the note. What i...
0
Future consideration
3
VOTE
Hierarchy report should focus on levels of strategy, not levels of workspace lines
What is the challenge? To set effective reporting standards in Aha!, it is important to have a consistent structure of strategic roll-up. For example, product goals connect to product line goals which connect to company goals. The hierarchy report...
0
Future consideration
2
VOTE
Top level record Epic (Feature) is automatically imported from the Jira integration when a user story from a different previously integrated Epic is added
What is the challenge? We expect product managers to work the integration queue to import Epics (mapped to Aha! Features) from JIRA into Aha!, since Epics are the top level record in our mapped hierarchy. We do expect user stories (mapped to Aha! ...
0
Future consideration
7
VOTE
Add AI query and summarization tools to the backend of Aha! Knowledge for internal authoring
What is the challenge? AI summaries exist on the frontend for customer use, but there’s no equivalent for writers working in the backend. What is the impact? Writers can’t easily query existing content, identify where updates are needed, or scale ...
0
Future consideration
4
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
5
VOTE
Apply workspace terminology in internal idea notification emails
What is the challenge? Notification emails sent to Aha! users regarding submitted or updated ideas use "Product" in place of "Workspace". Other emails, such as those around initiatives, use the "Workspace" term. What is the impact? If teams use "P...
0
Likely to implement
© 2025 Aha! Labs Inc.•All rights reserved