User story map

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

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

I want the user to be able to check a box to an Idea form to indicate if the idea they're submitting meets a certain criteria. Unless they check the box I assume it does not. A check box will allow every idea to be categorized without "requiring" ...

I’m not sure if Invision supports an API yet, but it would be an ideal integration for Aha. Right now, I think Aha does a great job of what I would call the front end of the funnel for product management: capturing ideas, managing a backlog, high ...

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

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

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