My ideas: Account settings
Sort by:
Trending
Status:
Future consideration
Showing 679
1
VOTE
3
VOTE
Support reporting across multiple Aha! accounts
What is the challenge? Large organizations with more than one Aha! account need to be able to report across instances. In some circumstances accounts cannot be easily merged. What is the impact? Ability to create cross account reporting while main...
0
Likely to implement
3
VOTE
Allow admins without a paid license to manage workspace hierarchy
What is the challenge? Some teams have central admins who do not manage work in Aha!, just help configure it for end users. These users have full admin permissions and help administrate the account. This is fine for most settings, but if a customi...
0
Future consideration
80
VOTE
Ability to change label names of Standard fields
In our org. we have 2 roles:
1. Product Manager - Who owns the Idea and is responsible for updating idea status.
2. Category Manager - Who should be informed when the idea is updated (Basically a watcher)
The above 2 roles are similar to what th...
9
Future consideration
1
VOTE
Ability to add comment to related record via automation
What is the challenge?
We're updating related fields on related records via automation. We would like to be able to add comments to those related records indicating what happened and what the fields were updated.
What is the impact?
It mig...
0
Future consideration
13
VOTE
Sort the list of release templates to appear in alphabetical order or set manually
What is the challenge? Large lists of release templates can be difficult to manage and sort. Not having a set list and being able to sort the order alphabetically or manually increases the time it takes to find a release template. This is also the...
0
Future consideration
2
VOTE
Support multiple billing entities and invoices for the same account
What is the challenge?
Consultants want to have a single Aha! account that they can use for their own work as well as specific client implementations, but they don't want to pay for all of them so they have to create multiple Aha! accounts inste...
3
Future consideration
12
VOTE
Delivery Risks - Ability to Inherent to Child Workspace
What is the challenge? If one product line (parent workspace) wants to implement Delivery Risks, we would need to individually go through the settings on each child workspace to configure. What is the impact? It is very time consuming for large pr...
2
Future consideration
16
VOTE
Option for workspace template to not override all settings when first applied
What is the challenge? When applying a workspace template, even if the settings are marked as unlocked in the template, once applied to a workspace the existing workspace settings will still be changed. This is not always the desired experience. I...
1
Future consideration
1
VOTE
© 2025 Aha! Labs Inc.•All rights reserved