As a very large account user, we have A LOT of custom fields and we are finding it very hard to manage. Our biggest pain point is that some of our Admins will update a custom field, that they believe is only being used by them in their product, an...

Given "Aha! is for the "why" and "what" and JIRA is for the "how."; Master Features are useless unless we can implement them alongside JIRA.

Add native integration trought Office 365 Sharepoint to output HTML5 contents from Aha! Roadmap.

Our software devs tend to use Github to track their work while also using it for their own feature updates. It would be nice to pull in issues which they create in Github into Aha! Likewise, upon initial setup of the Aha! account, all existing iss...

Currently the Aha-Jira integration has a fixed definition of which fields are synching in which direction. It would be beneficial if this integration could be defined per field. My current problem (see support request #134829) is that Aha sends ...

Business Need After creating Master Features I need the ability to see the estimates associated with features in a master feature. For example, today when a feature is associated with a master feature I can see the feature ID, name and status. I...

A more detailed Capacity Planning feature would allow us to better manage our roadmaps from the perspective of what is achievable based on our current resource levels. The following high level features would be included in a more robust capacity p...

Mobility is key to making a tool universally accepted in the workflow of a team. Look at the popularity of Slack as a result of the user experience of using the product across multiple platforms/devices. It would be great to have the core team fu...

Integrate Aha! with ProcessMaker.

As an Aha! administrator, I would like to control who sees banners from Aha! so that they don't blow past my banners thinking they are things from Aha! that they don't really need to read. I've learned from several of my users that they are not r...