Account settings
Sort by:
Trending
Status:
Showing 693
5
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
7
VOTE
Delete in Aha restricted to Admins expand to Custom roles
What is the challenge? Recently Aha! implemented a feature for restricting delete but once enabled only Admins can delete records. What is the impact? We have some power users who required delete permissions but do not need other admin priviliges ...
0
Future consideration
76
VOTE
Indicate required fields when editing a record
We need the ability to make standard and custom fields mandatory for existing records.
When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical inf...
14
Likely to implement
2
VOTE
Allow disabling avatar notifications for integration updates
What is the challenge?
With the new change that integration updates show as an orange circle on the avatar, I easily miss other notifications
What is the impact?
I always have integration updates, so I can easily miss when I have other not...
0
Future consideration
17
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...
2
Future consideration
3
VOTE
5
VOTE
Configure different Requirement types
What is the challenge? There is no visibility in Aha! what issue type the Requirement is in Aha!. In addition, we'd like to create Design tasks in Aha! which don't require sync to Jira, whereas we'd like to sync Backlog Items, Activities, and Bugs...
1
Future consideration
13
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
4
VOTE
Add ability to easily trace record history for deleted, copied or converted records
What is the challenge?
When a record is no longer discoverable through standard Aha! searches, there needs to be a straightforward method to access its historical details.
What is the impact?
Enhances audit trail capabilities
Addresses...
0
Likely to implement
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
© 2025 Aha! Labs Inc.•All rights reserved