Account settings

We have a large set of custom fields and the fields evolve over time. This means fields are withdrawn from use periodically, but there's no way to mark a custom field as archived and so prevent it from being available to include in a layout or rep...

What is the challenge? It is possible to update a user's current paid seat group via a CSV import by adding a column for that field and inputting their new group info, but there is no way to fully remove a user from a paid seat group via this meth...

What is the challenge? Difficult to implement continuous user monitoring processes without knowing user activity What is the impact? Privacy risk Describe your idea Add last login / activity date/timestamp to Users module

In Aha! we can only create record link with the 6 default relationship types, while in Jira the new relationship types can be added and are customizable. https://www.aha.io/support/roadmaps/strategic-roadmaps/collaboration/create-record-links We n...

What is the challenge? Inter font is not very crisp and difficult to read when presenting on large screens. What is the impact? Presentations and Dashboards that are displayed on screens in any forum aside from a desktop monitor become difficult t...

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

When creating custom fields for ideas or features we need ability to select which user group has rights to edit it. We created a field named owners, with multiple select options from which a product owner can select several names of people that ow...

Today you can identify which layouts and workspaces custom fields are actively used in. However, when looking to manage a large number of custom fields across a large organization, there is no way to determine which integrations are using that cus...

When user logs out of Aha! the logout message should be sent to the IdP. If user logs out of IdP Aha! should process logout message and also logout user. This should be supported for both Aha! and for idea portals.

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