User Story maps should be able to show Master Features and Features from multiple products. We have complex products that have to work together in order to deliver usable solutions. Any step that the user does (install, configure, receive certain ...

In our department we have developer teams working with Jira but also other teams for e.g. process improvements, consultancy... It makes no sense to track their work in Jira as they only need a simple board for their needs. Currently they use the M...

For instance to indicate which budget holder / budget code a user is linked to.

We have Improvement tickets in JIRA that we now (as new AHA users) want to migrate to ideas in JIRA. I have the JIRA integration created and would much prefer to import using the integration vs exporting tickets to CSV and then importing manually ...

We use the custom roadmap as our main overview. It will be really great if we have the option for dragging the features on this roadmap view as we can do on the starter roadmap.

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...

Emails sent from the ideas portal have a From address of support@aha.io The from address should be customizable to be branded just like the reply-to address. If my company domain name is example.com, I want to have the from email address be somet...

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...

It would be great if there is native integration of Aha.io with a Cisco Webex Teams bot much like the current Slack bot that is already available on Aha. Lots of users don't use email now and Teams is a great way to get notifications of posts and ...

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...