ADD A NEW IDEA

Account settings

Showing 506

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.
Guest over 5 years ago in Account settings 0 Unlikely to implement

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).
Guest over 5 years ago in Account settings 1 Future consideration

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...
Guest over 5 years ago in Account settings 0 Future consideration

Make timeframes respect chronology

Timeframes are currently treated as strings or labels within Aha!. As a result, ordering timelines will order them alphanumerically rather than chronologically. To a certain extent this can be worked around by specifying the year first and then ...
Guest over 5 years ago in Account settings 1 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,...
Oleg Yazvin over 5 years ago in Account settings 1 Unlikely to implement

Active Directory group integration for user authentication

We would like to give visibility (at least read only access) to Aha to a large amount of users (> 1K) in our organization however this is currently not practical as each user needs to be added manually one by one. Even when using SSO you still ...
Roman Hernandez over 5 years ago in Account settings 1 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 notificati...
Taylor Le over 5 years ago in Account settings 1 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...
Guest over 5 years ago in Account settings 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...
Florian Kette over 5 years ago in Account settings 1 Future consideration

Terminology customizations should persist throughout all screens when cascaded from Account level

We have updated some terminology for all of our products to use “Feature” (instead of default Master Feature), “Epic” (instead of default Feature) and “Story” (instead of default Requirement). Unfortunately, this update in terminology isn’t consi...
Kirstin Maurer over 5 years ago in Account settings 0 Future consideration