Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Account settings

Showing 646 of 9825

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...
Nathaniel Collum over 6 years ago in Account settings / Ideas 14 Likely to implement

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...
Manuel Froehlich 9 months ago in Account settings 1 Future consideration

Group custom layout types in settings

What is the challenge? In Settings > Account > Custom layouts, the primary record types are listed by default and additional layout types are show in a "More" menu. The layout types in the "More" menu do not seem to be grouped in logical w...
Madeleine Black about 1 month ago in Account settings 0 Likely to implement

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...
Max Robbins almost 2 years ago in Account settings 2 Future consideration

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...
Austin Merritt over 1 year ago in Account settings 0 Planning to implement

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...
Kristina Gass 9 months ago in Account settings 0 Planning to implement

Conditional Approve Workflows

What is the challenge? When you have multiple approvers depending on different conditions everyone received the same message What is the impact? Multiple users receive approval requests that might not apply to them. It causes confusion and...
Edgar Holguin 7 months ago in Account settings 0 Future consideration

Ability to add custom fields to the User table

For instance to indicate which budget holder / budget code a user is linked to.
Guest almost 9 years ago in Account settings 8 Future consideration

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...
Manny Pannu over 1 year ago in Account settings 2 Future consideration

Only Allow Users to Create Workspaces under the Workspace Lines They Own

What is the challenge? Users who have owner licenses can create workspaces or workspace lines not only under the workspace lines they own, but also other workspace lines they do not own. As admins of the Aha! account, we want to limit user's abi...
Hank Liu 8 months ago in Account settings 0 Likely to implement