Account settings

It would be extremely beneficial to limit the control of adding paid seat user to administrators whilst still allowing workspace owners to add viewers and reviewers to their workspace. Where adding users is required to be restricted to administrat...

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

What is the challenge? If certain entries in a user import CSV are invalid, Aha! does not process those as part of the import and shows an "Alert" with the failures. It does not identify which line(s) or record(s) in the CSV have the error. What i...

Today the idea or feature description is at the bottom of the display and it requires you to scroll down for the description. Can we control the placement of all of the fields which display for Ideas & Features including custom fields and idea...

Today under an Epic/Master Feature I can see related Features, but the layout only shows 2 fields: Feature and Status. To understand (for example) who that Feature is assigned to we have to click and open each feature. The option to "View in repor...

Aha! shows how many users are active in an account in two places: On the Billing page and in the CSV download of users on the Users page. For the Billing page, the number is calculated using the last login time, but for the CSV the report shows th...

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

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

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