In Aha, it's difficult to represent the relative effort required for different master features and features. Time is not the only consideration. For example, so features have dependencies that while not requiring heavy effort, will effect the dura...

It would be really useful to be able to list/count the total number of objects (requirements, features, master features, releases, initiatives, goals) across one or more products in a single pivot report. This could be done by making a product in ...

Right now ideas portals can only be created and managed by admins. Workspace owners cannot create an ideas portal or manage the portal for their workspace. As a workspace owner I should at least be able to create and manage ideas portals that are ...

Automatically removing shipped releases is not acceptable Such a big action should at least require users to agree to this change There's no easy way to find shipped releases This is a basic rule & also poses accessibility challenges https://w...

I have a long list of features that I imported for JIRA that I need to review and triage. I'd like to have the ability to quickly move something to a different release, and it doesn't appear to be possible to drag them to a different release when ...

Definitions for terms/concepts between product lines often vary. It would be great to be able to create a glossary/ubiquitous language archive where definitions can be linked to product lines or different products. This will help developers use bu...

For users who have more than 1 email address it would be useful to have 1 user associated with multiple email addresses.

It would be really great if the progress bar could be colour coded so that for each feature against an epic its status could be represented in its individual colour becoming progressively dark green as it more features are completed

This would allow us to collect all feedback, suggestions and product improvements with the option to push an Aha directly to our PMs.

I created a new feature in Aha! When I attempted to send the changes from Aha! to Jira, expecting a new Epic to be created in Jira, I got the following error: The following required fields could not be set on the epic: Fix Version/s. Please check ...