Account settings
Sort by:
Trending
Filter by:
Status
Showing 443 of 7723
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
6
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
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
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
36
VOTE
1
VOTE
Prevent non-billing admin workspace owners from adding paid seats outside their owned paid seat groups
The cure was determined to be worse than the ailment. Moved to an idea, tracked here: https://big.ideas.aha.io/ideas/A-I-13997 Currently there is an edge case where project owners are able to add users that take up paid seats outside the paid seat...
0
Will not implement
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
1
VOTE
Ability to Lock *Account* Layouts / Workflows / Scorecards
Use Case: We have Enterprise Layouts / Workflows / Scorecards that we would like to lock so that only a 'Collaborator' or Full Account Admin could unlock before updating / deleting Examples: We have a Scorecard that is the default that we do not w...
0
Future consideration
5
VOTE
6
VOTE
