As we continue to expand our use of Aha, one issue that has come up is that within a given product, there are different types of work/requirements that require different types of information. We're adding more and more custom fields, and it's star...

We have two portals, one for internal users and one for customers. The customer portal only needs a simple list of categories - no children categories. The customer portal is submit only. For the staff portal, after a product manager has looked at...

At the moment all personas & competitors are inherited from the levels above even if some do not apply. In order to avoid duplication by defining the same persona/competitor over and over at the product level it would be much better if persona...

As Aha! reporting features are not advanced / flexible enough to meet all our data analysis requirements, it'll help if it is possible to connect Tableau with Aha! directly so that we could handle the analysis by ourselves. More importantly, Tabl...

Aha! Develop has excellent support for SAFe in its program increment, sprint planning and program board functionality. Teams who are doing PI planning in Aha! Roadmaps with their engineering teams in other development tools are not able to benefit...

As a creator and publisher of presentations to my internal stakeholders and customers, I would like to have visibility into usage information for each presentation. Information I would want to see include page views, unique user views, and time sp...

Drag and drop is onerous only available in full release view. User should be able to directly enter rank position (or even before/after another ticket reference.)

It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.

When promoting the Work Request to an object, copy all existing custom field values that are shared across all Ideas (with same API key) from the originating object to the new object

My org's hierarchy is huge; and to reduce the amount of administration all user have the ability to (at least) see everything. It would be great if I could "favorite" or "star" or "pin" products and lines from the hierarchy so that I can always ge...