-
Disable custom fields, tables, etc. so they can be seen where previously used, but aren't available for continued use
As explained above. It will help when a custom field is deprecated, but new users don't realize they shouldn't use it.0 Unlikely to implement
-
Ability to require Paid Seat Group selection
We have Paid Seat Groups established, and have an internal policy that all licensed users need to belong to a seat group. However, we still have admins who forget to add this because they aren't promoted for it when adding a user from products>... -
Ability to disable "New User" invite when SSO is enabled
When SSO is enabled, there should be an option to disable the "New User" tab on "Add User" screen. This would reduce some confusion on how users get access (they just need to sign in vs. being invited/registering). -
Ability to distinguish between users with the same real name
In a large organization (3000+ folks, like mine), there are bound to be users who have the same first + last name, as is used in Aha when @-mentioning a user. When using this @-mention feature, there isn't a way to distinguish between these users,...1 Likely to implement
-
Customize the the release date strings
As a release planner, I want to be able to customize the strings that we use to identify internal and external release dates so that the description has a meaning that makes sense to the people in our company (currently it's "Release date (interna...0 Future consideration
-
Floating License
We have around 10 users that need to use AHA! but only 6 that generally ever need to use it concurrently. Right now, we accomplish this by activating/deactivating accounts as needed. It would be great if the user licenses tracked user concurrency,...0 Unlikely to implement
-
Stop Product Hierarchy from collapsing after each edit in Product Configuration (Account Settings > Account > Customizations > Configure Products)
After editing the product configuration the product hierarchy always collapses to the top level. This is very inefficient when multiple things need to be changed. Ideally the product hierarchy structure stays exactly at the same level after the ed...0 Future consideration
-
"Out of office" user setting
Allow users to indicate when they are (or plan to be) out of office. This would let you avoid assigning work to teammates when they're unavailable. So, if I created a to-do for someone with a due date of when they're OOO, I would get a notificatio...
0
Future consideration
-
Managing Persona Fields
When creating and modifying Personas in Aha!, there is an ability to create/modify custom fields on the Persona via the "Manage fields" menu link. When I click on that link, I am navigated to the Custom fields screen within the Account settings. I...0 Future consideration
-
auto contrast of text in tag elements
If I select colors for tags and categories tags, I expect the application to automatically choose a better contrast for the description text, because if the background is too light, the font remains white and can not be read anymore. Define a thr...0 Future consideration