Account settings

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

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

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, when assigning records (features, stories, etc.) in a workspace, the dropdown list includes all users with access—regardless of their role (Owner, Contributor, Reviewer, Viewer). This can lead to mistakes, as Re...

What is the challenge? When a workspace is archived, its custom layout is no longer associated with any workspace—it disappears from the custom layouts "Used in" list. As a result, you may choose to delete custom fields and custom layouts that a...

What is the challenge? For teams that want to delete many custom layouts, it's time-consuming to do it one-by-one. What is the impact? Teams need to spend significant time manually deleting custom layouts. Describe your idea Enable t...

What is the challenge? Large organizations with more than one Aha! account need to be able to report across instances. In some circumstances accounts cannot be easily merged. What is the impact? Ability to create cross account reporting while main...

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

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

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