Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Account settings

Showing 635

Conditionally required fields

What is the challenge? Currently, a field cannot be required based on the value of another field. A few example use cases: If field A is selecting a Category from a dropdown menu: "User Experience", "Performance", or "Security," then field B w...
Guest 3 months ago in Account settings 0 Future consideration

Ability to configure scope of selection for custom "users field"

What is the challenge? Based on our use case, we need the ability to configure the scope of selection for the custom "users field" What is the impact? Not able to configure the scope of selection. Describe your idea Need ability to configure the s...
Hank Liu over 1 year ago in Account settings 0 Future consideration

Multi select workspaces or workspace lines when assigning permissions

What is the challenge? The Bulk edit feature allows you to grant access to either a single workspace or an entire workspace line (which includes all child workspaces). However, you cannot multi-select specific workspaces to grant access to when ...
Chris Quigley 3 months ago in Account settings 0 Future consideration

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 8 months ago in Account settings 1 Future consideration

Improvements when duplicating workflows

What is the challenge? When duplicating a workflow, Aha! doesn't copy across the template text or the status custom field layout to be used (Enterprise+ only) to the new workflow What is the impact? The new workflows aren't exact copies of...
Justin Woods about 1 month ago in Account settings 0 Future consideration

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

Introduction of further customization user permissions

It would be wonderful if Aha! had the option to customize user permissions when it comes to adding or editing ideas, adding or editing features, etc. For example, one user could have permission to only work with requirements while not having the o...
Guest about 6 years ago in Account settings 8 Likely to implement

Time frame - add calendar dates to be able to support reporting

What is the challenge? Currently, time frames are text only choices, there is no respective date range, therefore, you cannot effectively utilize time frame for reporting when you want to sort in a particular order or pull all initiatives, goals...
Karie Kelly about 1 month ago in Account settings 0 Future consideration

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 over 1 year 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 Likely to implement