Account settings

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

When defining features in a workspace, you should only need access to utilize valid values from selected workspaces. Each workspace owner defines and reports on their valid values very differently. When all valid values from every workspace are di...

Being that we don't have a reliable user access management tool, our Admins clean up the users if no activity after 90 days. Unfortunately, there isn't a way to filter this, so I must click every user on the page in order to disable in bulk. Click...

Aha Score is a standard field in Aha and like many others, you still can configure it based on your business requirements. This is why it would be good that the reviewers' users be able to understand the metrics under that score and have quick vis...

I have a number of different products all of which require their own tags. Each product is sufficiently different that a tag in product one would not make sense in product two. Currently I can see all of the tags for product two in product one and...

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

Who would benefit? Users/organizations that don't follow a standard/defaulted fiscal year What impact would it make? Allowing an organization to set exact perimeters for their fiscal year will allow for accurate reporting. Currently, if one of our...

Who would benefit? Product Owners/Managers What impact would it make? Easily be able to access linked record information from within the parent record such as engineering phase and engineering target date (custom fields.) How should it work? Enabl...

We would like data to be passed using shared fields across objects the same way promoted objects work. Today, if a field (e.g UCMGID) exists with same API key in IDeas, Features, Epics etc, that data will be passed when the Idea is promoted. What ...

What is the challenge? For large scale implementations it requires a blend of general Aha! documentation and internally created documentation to provide users with a complete picture. In app we are limited to only Aha! resources What is the impact...