All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6289
1
VOTE
Customized whiteboard zoom
Who would benefit? Anyone collaborating with the new Aha! Whiteboards What impact would it make? It will improve collaboration, since the launch of whiteboards, I now have another reason to keep all my work in one single place. However, when shari...
1
Future consideration
2
VOTE
Customer interview snippets linked to research
Who would benefit? PM's doing product discovery What impact would it make? I love the new capability to link notes to items through the research tab. This has brought so much more of our collaboration together in Aha (though allowing non account h...
1
Future consideration
2
VOTE
Automatically translate ideas to different languages
Who would benefit? Multi-national customers using Aha! to capture ideas What impact would it make? Foster collaboration on ideas across different languages How should it work? If user A enters an idea in English but user B can only speak German od...
0
Future consideration
7
VOTE
Aha - get Audit history for the custom tables
The data in the master table which has the reference in the Custom Table was modified. when we investigate the history of the custom table, it shows the history of information. But when I look into the audit of the custom id, the history is not sh...
0
Future consideration
14
VOTE
Ability to create a shared webpage as a report editor
There appears to be a gap on how shared webpages are configured. Currently only the original creator of the report can create the link for a shared webpage. Often, other people who are designated editors to the report, need to download to send out...
1
Future consideration
4
VOTE
5
VOTE
Map Created By User from Jira
Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
1
Future consideration
2
VOTE
Consider inherited values when copying workspace settings for workspace templates
Who would benefit? Any users creating a workspace template from an existing workspace. What impact would it make? Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings. For example, at the wo...
0
Future consideration
11
VOTE
Personas can be 'mentioned' using # in a text editor
As a #productmanager, I would like to easily use a # to reference personas when I am defining a feature. This would work just as it does when using a # to refer to features or epics - typing #persona_name would search and find that persona. A litt...
3
Future consideration
12
VOTE
Allow custom fields to be shared across items
We have some of the same custom fields on Epics and Initiatives that are drop down lists. Not only do we have to create them on each entity, but when the selections are updated, we have to update both fields manually. Sometimes these selections ar...
2
Future consideration