Account settings
Sort by:
Trending
Filter by:
Status
Showing 687 of 9643
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
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...
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
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
4
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
96
VOTE
Allow sorting records in custom tables
Custom table records are currently sorted by order of creation. Since users often create more important/common records first, the important ones end up at the bottom of the list. Instead, allow sorting these records via drag-and-drop (or at least ...
17
Likely to implement
14
VOTE
Allow immediate delete for brand new workspaces
Currently workspaces can only be archived. They cannot be instantly deleted. This is a great safeguard to prevent real workspaces from actually being deleted. However it causes problems when you accidentally create a workspace as a line, or vice v...
0
Likely to implement
4
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...
0
Future consideration
14
VOTE
Amount of changes made by a user when Account Level permissions
What is the challenge? Business Problem to Solve: Utilization report: We would like to know who is utilizing the Aha Account Level? How can we manage the amount of changes made by a user when Account Level permissions have been granted? License co...
1
Future consideration
11
VOTE
Quick navigation to settings pages by name
When working with Aha! customers, one part that slows down users as they set up their account is figuring out how to navigate through to the page they need. Let's say I am helping a customer add a custom layout and statuses to their ideas and idea...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved