Account settings

What is the challenge? Large lists of release templates can be difficult to manage and sort. Not having a set list and being able to sort the order alphabetically or manually increases the time it takes to find a release template. This is also the...

What is the challenge? Recently Aha! implemented a feature for restricting delete but once enabled only Admins can delete records. What is the impact? We have some power users who required delete permissions but do not need other admin priviliges ...

What is the challenge? Business Problem to Solve: Utilization report: We would like to know who is utilizing the Aha Account Level? How can we manage the amount of changes made by a user when Account Level permissions have been granted? License co...

What is the challenge? Some teams have central admins who do not manage work in Aha!, just help configure it for end users. These users have full admin permissions and help administrate the account. This is fine for most settings, but if a customi...

It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...

It would be useful to be able to customize layouts. For example, add section markers to separate fields for a more organized view, add helper text underneath field names that doesn't disappear as soon as the user starts typing, and arrange related...

What is the challenge? Currently, status category is not a field that can be added to a customised card layout What is the impact? Status category can be indicative of the higher-level status grouping of where an item is at in our product ...

We have multiple organizations/Business Units/Groups with their own product line in the hierarchy. We would like to be able to make them admin of just that area so that they can make the customizations they need without negatively impacting produc...

Often settings like layouts, terminology, and navigation for parent lines may be purposefully different than workspaces. It would be helpful to drive standards for lines by allowing templates to be applied at those hierarchy levels. A few examples...

It would be very useful to be able to set read-only permissions for some fields (either standard or custom fields) based on permissions, or - even better - permission groups. In fact we have some fields on Features and Ideas that should be maintai...