Account settings

Who would benefit? Customers who are required to share feature documentation with enterprise or large government clients What impact would it make? Ease of hiding internal information or displaying only customer relevant information How should it ...

What is the challenge? Working out who is Owner and Contributors across all Workspaces and Lines in order to be able to review whether additional seat needed What is the impact? Makes it so much harder to manage Describe your idea Mu...

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

Who would benefit? All users What impact would it make? owner can customize the homepage they would like to highlight for team members. (for example: quick start guide note) How should it work? Owner can set default homepage for each workspace.

The current behaviour is for a workspace template change not to apply to workflows because of the risks of changing many status mappings. For our use case of workspace templates, we would prefer that all workflow changes are automatically applied ...

What is the challenge? Making billing changes in advance of subscription renewal requires communicating with Aha! support What is the impact? Since information is not even visible in the user interface, it's confusing. Because the details aren't k...

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

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

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