Currently, when someone performs a change to a score card, only the top-level score change is captured rather than each of the individual sub-scores.

While reviewing intiative in Kanban, team working on it could see the criterias of a status

Let's say, I have an important major version release slated for Dec 2019 and I have monthly releases with several features planned with every release. I want to create a gauge chart that would show progress from 0% to 100% as I releases are shippe...

What is the challenge? When users leave the company and their Okta accounts are disable, their Aha user accounts remain active What is the impact? This impacts our available user license count in Aha Describe your idea Improve the Okta integration...

It would be great to be able to customize column headers in the prioritization view. My main use case is to shorten field names so that I don't need to scroll horizontally.

We have implemented a custom field on the proxy vote of Customer Value using a predefined choice list of 5 options (scale Low - Top priority). We'd like to be able to cap the absolute count number of ideas that can be assigned a value of Top or Hi...

Currently, the Visualization link in the Release Record links only shows the Release Name and Release Status. I'd like to add other fields such as, but not limited to, Release Date.

When enabling capacity it is not real intuitive as to how capacity for a release is set within the Features Board; especially when it is originally showing as N/A.

Add three weeks, five weeks, six weeks, seven weeks, three months, four months, and five months to the choices for when each automation step is due.

Add Features to a Master Release because some features are unique to the combination of sub-releases