Currently Ideas that are emailed into the portal are not visible. I would like to see this be a configurable value so these can be made visible automatically versus having to manually update the emailed in Ideas.

What is the challenge? We have a customer facing portal and an internal portal. We are trying to track activity and engagement by portal, but I cannot seem to get the specific details about what portal a vote was submitted in. What is the im...

For most standard Aha! Record types there is a 'URL' field available for reporting. However Custom table records do not have a URL field in reporting. The use case here is for getting access to a custom table record from outside of Aha! when a rep...

What is the challenge? Users can see everything on the Feature board and some people may talk about futures or ideas before they should publicly. What is the impact? Product ideas get released for socialization too soon, or when they never...

What is the challenge? Currently you cannot export or create a list report of the users in an approval group. What is the impact? Auditing capabilities of users in a workspace approval group. Describe your idea Found in Settings > Workspace >...

I typically go to Release > Details when I want to look at a shipped release. I change the "Release Settings" filter to "Show shipped releases". When I do this, it lists the current releases at the top, followed by all of the shipped releases. ...

The list of archived timeframes can get pretty long and since not active, really doesn't need to appear so hiding them would be better

We have a large organization with multiple divisions under using Aha!. Need to create a single Notebook that can host all Roadmaps for specific division for easy access. Limit of 40 is very low. Need this to be in 80-100 range.

When using Starter Roadmaps, if the workspace has master features (epic) enabled, would be great to have them also available there.

As a user, when creating a new Aha Initiative or Feature, I would like the ability to choose whether the Aha Initiative/Feature/Requirement should be mapped as a JIRA Epic, User Story, or Requirement, so that I can have more flexibility when creat...