Skip to Main Content
ADD A NEW IDEA

Account settings

Showing 513

Allow ability to limit valid values in Feature fields to only display relevant values for the workspace.

When defining features in a workspace, you should only need access to utilize valid values from selected workspaces. Each workspace owner defines and reports on their valid values very differently. When all valid values from every workspace are di...
Karla Johnson over 2 years 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 about 2 months ago in Account settings 0 Future consideration

Adjust archived/deleted workspace association to workspace templates

What is the challenge? When a workspace is archived it should no longer display as associated to a workspace template. What is the impact? Since users are not able to hard delete workspaces, they will see an inflated number of workspaces associate...
Kristina Gass about 2 months ago in Account settings 0 Future consideration

Record level permission restrictions

What is the challenge? Some features or initiatives are sensitive, so we would like to be able to set record level permission restrictions What is the impact? Anyone who might come across work that isn't being widely publicised in the org Describe...
Nerissa Muijs about 2 months ago in Account settings 0 Unlikely to implement

Determine default Home Page for All Users

When a user logs into Aha!, the first page they see is the page "How Aha! works". Our users are reporting that this is confusing, as they want to navigate to a page within the product itself (i.e. Feature Board or Releases Overview"). Users arrivi...
Matt Howard about 6 years ago in Account settings 8 Future consideration

Provide the ability to choose where custom tables are displayed in the navigation

The navigation change implemented on 03/13/23 resulted in users having to access custom tables via the workspace settings. It would be great if we had the ability to move this back to the previous location of the Notebook tab (previously 'info').
Niall Gallagher about 1 year ago in Account settings 1 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 about 7 years ago in Account settings 8 Future consideration

Re-use custom fields in any item type

It's cumbersome to need a unique custom field for the same data across different item types. It would be more efficient to be able to use a single custom field in multiple item types.
Max Cascone about 6 years ago in Account settings 7 Future consideration

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 over 4 years ago in Account settings 3 Future consideration

Custom terminology for new "Roadmap" menu

Currently, you can create custom terminology for most of the menu's in Aha and other terminology. I would also like to be able to rename the Roadmap menu (for example to Reports, as this is more meaningful for our company) as the new Roadmap menu ...
Julie Edwards over 5 years ago in Account settings 8 Future consideration