Currently the custom fields that are relationships to other Aha! records (e.g., workspace field) allow users to choose one or more workspaces. In many of our use cases, we need to limit the choice to one and only one record. In such situations, gi...

The features roadmap is one of the most informative views as a PM. I would like to use that view and group the items in each release by a custom field that only has two choices. However, the only field this roadmap allows grouping by is feature ca...

With a digital first mindset on the rise and more tools like Slack being used for asynchronous communications and collaboration, the ability to create workflows from within Slack to be able to submit an Idea or create an epic or feature would impr...

Using the strategic roadmap, we would like to be able to expand each initiative to view its child features, while viewing only the releases assigned to this specific workspace. As it stands, this roadmap view shows us every linked release across e...

In a list view, I'd like the ability to programmatically set a filter to the user who is viewing the list table in that web browser. I'm creating a set of audit style views. I'd like to filter the user programmatically to the user in that view. Ki...

We would like a way to embed info pulled in from another source into the title page. Currently we like to show team leads on the title pages across 10-12 notebooks. The issue we have is from time to time the leads may change and this makes it so w...

When reports initially display, the columns auto expand to the widest - at times, this can exceed even the onscreen browser width. By default, have a set width to avoid this issue. Also, allow the column headers to wrap where the column headers li...

Many marketing teams use Aha! to create and manage their marketing campaigns and roadmaps. This use-case typically involves representing campaigns as Aha! Releases and generates many more releases than a software development use-case would (typica...

It would be nice to have the ability to vote on feature cards that Product Managers have created within a given project within AHA. This way the functionality would not be limited to votes on features that have been promoted from the Ideas Portal ...

A product manager will frequently switch between the priorization screen and the board to view features. If the drag-and-drop stack ranking is used and without product value, then the card sorting drop-down excludes this field. The workaround is t...