Account settings
Sort by:
Trending
Status:
Showing 435
49
VOTE
Dedicated Integration User
It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
8
Future consideration
32
VOTE
Custom terminology for new "Roadmap" menu
Currently, you can create custom terminology for most of the menu's in Aha and other terminology. I would also like to be able to rename the Roadmap menu (for example to Reports, as this is more meaningful for our company) as the new Roadmap menu ...
7
Future consideration
54
VOTE
43
VOTE
As an Admin, I would like the ability to easily see and filter which custom fields are being used by which products and product lines
As a very large account user, we have A LOT of custom fields and we are finding it very hard to manage. Our biggest pain point is that some of our Admins will update a custom field, that they believe is only being used by them in their product, an...
6
Future consideration
37
VOTE
Determine default Home Page for All Users
When a user logs into Aha!, the first page they see is the page "How Aha! works". Our users are reporting that this is confusing, as they want to navigate to a page within the product itself (i.e. Feature Board or Releases Overview"). Users arrivi...
6
Future consideration
14
VOTE
Automation rule that adds a new row to a custom table
In my use case we have a custom table on releases to track changes to the release date. I would like to set up an automation rule so that "when the release is updated and the date field changes to anything" then "add a row to the custom table with...
1
Future consideration
5
VOTE
Follow custom terminology in Pivot reports to reflect customized terminology of where the report was originally built, not where the report is run
Pivot table headers use the terminology from the workspace they are being viewed. I want to see the terminology that is used from the workspace line where the pivot table was built. By not reflecting the customized terminology we are effectively i...
1
Future consideration
5
VOTE
Follow custom workspace line terminology when viewing Roll up to workspace goals
When a workspace line references its parent, the naming of that parent should match the parent level, not the workspace level. By not reflecting the customized terminology we are introducing layers of confusion for the team members who don’t spend...
1
Future consideration
5
VOTE
18
VOTE
The ability to have a tool tip for a standard field
Aha Score is a standard field in Aha and like many others, you still can configure it based on your business requirements. This is why it would be good that the reviewers' users be able to understand the metrics under that score and have quick vis...
2
Future consideration