Application

The concept of favorites exists in many places in Aha! — favorite reports, favorite attachments, and even favorite notifications. One place I’ve realized that I’m really wanting this functionality is with the records themselves. I would love to be...

Communication between Aha! and Salesforce is essential and by allowing comments made in Aha! to flow into Salesforce, this helps save time and alerts Salesforce-preferred users to be kept current with the latest information entered from Aha!

When we build reports in Aha, it would be nice to display the option to show the product logo on the columns under the product. Right now the reports look like a spreadsheet report, adding logo's will make the reports look richer.

When you have the Initiative Tiles in the Strategy > Details view there is a tile to display the Initiative, etc. It would be nice to have the Release be automatically an element of the tile The issue is trying to determine what initiative is...

Allow workspace types to be applied at the product family and division level to allow for unique workflows at higher levels

In our large organization, top-level Product Line owners should be able to add new, sub-Product Lines without needing Admin access. Admins have the power to change many global settings that could impact the work of others in the organization. I'd ...

When a ticket is created by the Zendesk integration, and a reference to the originating ticket to the Idea in Aha.

What is the challenge? We have a complex product portfolio and like to produce a roadmap view that shows releases attached to initiatives. The problem here is that we end up with a very tangled roadmap with releases or features flowing into multip...

You can currently add a dependency between features and also between releases. It seems logical that if two dependent features exist in separate releases then the releases are by definition dependant on one another. It would be nice to see this on...

I often mark requirements as "will not implement" in Aha (rather than deleting them) just to keep a trail of requirements we've discussed but decided aren't needed. Then when I push to JIRA from Aha, it brings all requirements for a feature over.....