Account settings

What is the challenge? Consultants want to have a single Aha! account that they can use for their own work as well as specific client implementations, but they don't want to pay for all of them so they have to create multiple Aha! accounts inste...

What is the challenge? The “Watchers” field changes are not captured on the history logs and therefore we are unable to explain why people are added as a watcher to a ticket. What is the impact? Be mindful of the potential security implications of...

Who would benefit? Users who have enabled the Delivery Risks feature What impact would it make? It would allow to immediately capture on a feature if there is a dependency on a body of work that has not been scheduled. How should it work? Add a fu...

What is the challenge? People often have an Epic or initiative reference number, but don't know the workspace name to request access. It would be helpful to have a prefix look-up tool with the Product look-up tool What is the impact? Users need th...

I would like to explore if Aha can provide that automation wherein if Admin users like owner/Contributor who have not contributed to Aha in the last 1 month or so (which can be configured) and downgrade the same to Reviewer/Viewer so that those li...

If I want to manage (e.g. replace tags by others) my custom field choices (of type predefined tag list) I need to search a long time because they are not sorted alphabetically. Please sort them alphabetically.

What is the challenge? We've defined a set of custom fields as Predefined Choice Lists which all have a common set of Choices. The fields are to show levels of Platform Adoption across workspaces. We have ~13 platform services and want to visualis...

I would like to have the ability to set an automatic deactivation of user accounts after XX days of inactivity. Use Case: As an admin with a large user base, I frequently have users moving between groups, changing responsibilities, etc. Sometimes...

I would like to have a way to manage my Aha Account in order to disable internal user's ability to generate an API Key?

We would like to have a core set of common fields used in the field layouts for all products, but there will still be a need to support custom fields needed only by a subset of products. If we could have products inherit a custom field layout and ...