Editing permissions are currently based on memberships in a product, there is no option to control them by individual users. In a situation when we have a critical report that we do not want everyone that is part of a product to edit, the only oth...

Loving the calendar reports but one key thing is missing! We'd like to put the product name on the feature card and don't see the option to do so in the settings. We try to keep our product prefixes short, and now, that seems to be our only option...

The workspace needs a more permanent architecture planning section. The Draw.io functions within notes section are very helpful but are attached to features and releases, which tend to be transient in nature. An architecture workspace would be mor...

Currently, throughout Aha! and in the documentation the term Capacity is used loosely to imply both Capacity or Demand. This is creating confusion amongst our users and we request that Aha! clarifies the terminology to distinguish between demand a...

The ability to give customers a set number of votes that they can use each quarter or year. Using the functionality where votes can be configured such that users can apply multiple votes to a single idea or across multiple ideas. For example, cust...

Based on our organizational structure and roles and responsibilities the "Reviewer" role does not have enough permission and the "Contributor" role has too much. Specifically, we're looking for a role that removes "add manage strategy" from the co...

Who would benefit? All reviewers and contributors What impact would it make? No more manual action per documents How should it work? Reviewers should be able by default to edit a document, and not for an admin to have to change from "review" to "e...

The Ideas Advanced plan currently supports ideas portal translations in English, Spanish, German, French, or Dutch. Having portal translations in Japanese would be helpful as well.

As a user I would like to integrate Stories On Board with my Aha Account.

I think an additional column is needed on the export to indicate if the user has been disabled or not. I’m seeing my user export list grow, but the CSV doesn’t readily show you if a user has been deactivated (their original permissions stay reside...