As a creator and publisher of presentations to my internal stakeholders and customers, I would like to have visibility into usage information for each presentation. Information I would want to see include page views, unique user views, and time sp...

Our organization promises to review and take some action on any idea that receives over 25 votes. We don't count internal votes toward that total, but internal votes will push it over that threshold. The main problem is that the customers only see...

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

The current Aha! Kanban board does not provide the flexibility other tools such as SwiftKanban provide. Is there any plan to build an integration into Swift Kanban and/or is there any plan to build out a more robust kanban board within Aha! We hav...

What is the challenge? In both the Feature Workflow board and the Ideas Board, teams that use a shared Status workflow may not all utilize every status. During some key planning exercises, not all statuses may be required or pertinent. What ...

This is regarding the JIRA integration feature: Automatically Import New Records: Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, master...

What is the challenge? Archived work pages only hold a handful of workspaces What is the impact? Takes a TON of time to go through each page when there is 50+ pages in some cases Describe your idea Add a search-bar on top or revert t...

What is the challenge? Unable to add record link fields (Goals field, Releases field, etc) to Ideas Portal submission layout. What is the impact? Individuals who are responsible for reviewing ideas are required to reach out to the idea cre...

What is the challenge? AI summaries exist on the frontend for customer use, but there’s no equivalent for writers working in the backend. What is the impact? Writers can’t easily query existing content, identify where updates are needed, or scale ...

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