I currently have to create flow diagrams outside of Aha and paste in a static version that others can not change. This is very restrictive and does not follow the collaborative flow I like to use. https://www.gliffy.com/

Who would benefit? Product Managers and other roles managing requirements during the lifecycle of a product What impact would it make? In many cases (e.g. regulated products) once a requirement is formally approved, it cannot be updated unless it ...

Today users are not using search field and instead go straight to 'create new idea' and/or relying on the title bar search when they go in to create a new idea which is only causing duplicates and creation of requests for capabilities that already...

e.g. I have a custom table with a user field, when I put it into a pivot table and use the count method, although I have two entries under that field the count method only shows up as 1 when I would expect it to be 2

As a PM, I want to be able to see all the features in the user story map all tidied together. Right now if I build a story map before putting them in releases, the features are all spaced out when added to features forcing me to move each feature ...

Who would benefit? Our internal portal users - account managers, customer success managers, etc who want to see which ideas a specific client is interested in. What impact would it make? We would no longer need to provide these uers with reports f...

Who would benefit? Those using releases What impact would it make? Less manual work How should it work? Have an option for Release status to update based on progress of features/epics in the release. The progress can change based on settings, so i...

In addition to exporting views to PDF, tt would be helpful to export views to Keynote.

We have created a custom field named "Product" which is of type "Products Field". In our Jira 2.0 integration, we want to map this field to a Jira field called "Component/s". We can see "Component/s" on the Jira side but the "Product" field is not...

I would like to map the release reference number field for Epic between Aha! and Azure DevOps Integration. But I can not find it in the field mapping of Epic. I found the release reference number field for Feature, not Epic, at field mapping of Ah...