Application

I am using the new Template capability to provide guidance for populating Initiatives / Capabilities (Features) via a standard format. Unfortunately, to use this feature I am required to include the Description field in the Create Layout. This res...

The status should be applied to a BR (feature) when a Need (epic) is changed or ask if we would like to align. I find much time is wasted doing this and often BRs are missed.

We want to report on our business units' compliance using standard custom layouts for Workspaces which we have set up. Therefore I am trying to extract the AHA metadata underlying the Custom Layouts, and will then match a Workspace custom fields a...

For some customers, we would like to open-up additional fields for Idea submitters to capture additional information. For example, we ask some of our VIP to add their priority to the Ideas that they submit (but not open for all customers). For exa...

Currently when personas are moved from a product to a product line, and presumably to other products, any custom fields not shared between the two products are "lost". This leaves the user, i.e. me, in a panic because it appears that all of the da...

When searching for entries in drop-down lists in Aha!, do ignore diacritic marks/accents on letters so that searching for e would find é as well.

A search inside Aha only matches on Name and Reference while the portal does allow you to search the description. The portal should be more functional than the complex searching options found in Aha!

The main goal of this feature request is capture user task descriptions and usability findings from user studies, and link them to planned features, such that I can stop speculating which feature will have an impact on my product and start measuri...

The ability to a capacity and monitor feature work against capacity is very useful but there are some small issues that prevent you from just monitoring the progress bar. The story points for Requirements marked will not implement are still counte...