All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5994
2
VOTE
New section under Strategy or Info for definitions/product functions.
Our Product has multiple functions/modules. With each module there are some terminologies and concepts that need to be defined. I can use notes to create a document but that that can get messy really quick. I see this area working similar to how P...
0
Future consideration
1
VOTE
Hide the title on shared webpages
I often embed Aha shared webpages in Confluence and Notion. These apps require me to give a name to the page which is often the same as the name I give to the note or roadmap that I embed in the page. This results in the same name appearing on the...
0
Future consideration
1
VOTE
Allow Idea viewer to update proxy votes (not raised by you)
As it currently stands Idea viewers are not able to update votes, which were not raised by them. There are multiple reasons why the viewer may want to update existing votes: 1) reflect the latest severity / impact (e.g. downgrade / upgrade) 2) mod...
0
Future consideration
2
VOTE
Block default customization from being modified
Anyone with customization permissions can modify the Default workflows, scorecards, time frames, etc. Without removing the option to set new default, why not blocking the default from being modified? this will allow an encourage users with the rig...
0
Future consideration
2
VOTE
Don't automatically open links in notes/descriptions in a new tab
When you try to open a link from a note/description in a new tab, some javascript automatically opens the link in a new tab and changes the focus to it. Opening a link in a new tab should be done in the background, like when done with the middle m...
0
Future consideration
2
VOTE
Allow each team to provide an independent set of tags on a feature
Looking at the tags field on a develop feature, it inherits all of the tags from my main roadmaps workspace. This isn't the behaviour I'd expect, I would expect a develop team to have its own unique set of tags of primary relevance to them. In pla...
1
Future consideration
2
VOTE
Extend the 'Lock fields based on Status of the record' to Custom Tables
We use Custom Tables in many workspaces to track dollar savings.Once a project reaches a certain status these committed savings should be locked. It would be a great enhancement to be able to do this with Aha!'s 'Lock based on Status' functionality.
0
Future consideration
1
VOTE
Manage Users admins shouldn't be allowed to change the admin roles for themselves or other users
People in our organization are given the Manage Users admin role in order to manage the licenses associated to paid seats. However, the Manage Users admins are able to assign additional administrative privileges to themselves & other users. Am...
3
Future consideration
1
VOTE
Prevent users of adding comments and/or to-dos in custom templates
Users get confused and add comments about the feature in the requirement card. Same happens with to-do. As a consequence, the progress is calculated wrong and the reports don’t show the information you want, like “last comment”.
0
Future consideration
1
VOTE
Provide help with consequences of merging custom fields
The Aha! KB article on merging and converting custom fields explains that there are implications for integrations and reports when merging fields. Specifically: If an integration included the old custom field, you will need to update the field map...
0
Future consideration