My ideas: Account settings

What is the challenge? In order to cover all the use cases of a user getting a workspace access error, you have to know about two different settings: Account->"Security and Single sign-on"->"New user instructions", and "Account->Profile-&...

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 ...

It would be great if Aha! provided a step-by-step wizard to setup the Capacity Planning for Teams feature, very similar to how the current integration setup wizard functions. As an admin, I am not quite sure the sequence that I need to set up the ...

What is the challenge? The custom types configured in the features status/workflow configuration display with the field name "Type" on the feature layouts. The "Type" term cannot be customized. What is the impact? The term "Type" doesn't align wit...

What is the challenge? The custom types (configured in the features status/workflow) are only available for features. This type categorization is needed for other record types, including epics. What is the impact? The current workaround is to use ...

We have many workspaces that would benefit from the ability to add pages and views to the top nav. For our use case, we would like to: Add sub pages to existing top nav items Add new top nav items to create a folder of quick links We do not have a...

Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users. It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...

When background jobs fail we are not able to see what caused the failure. It would be helpful to see which records(s) caused the issue so that the errors can be resolved quickly. Recently saw this with a bulk update job error - the message indicat...

To avoid removing the integration template when a workspace is archived, there could be a warning or prevention during the archiving process.

Appreciate this can be achieved via SSO but it would be a great admin feature to have on the AHA side of the interface. As an admin i would like to be able to set a default permission for product & role rather than have to dialogue with our IT...