Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Pinned ideas

PINNED Chrome extension to capture feedback from anywhere [Shipped!]
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...

All ideas

Global feature to filter out internal votes displayed everywhere in Aha!, especially in the Ideas Portal

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...
Guest over 3 years ago in Voting 4 Future consideration

Hide Idea Categories From Portals

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...
Guest almost 11 years ago in Ideas / Ideas portal 9 Future consideration

Integration with Swift Kanban

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...
Guest over 7 years ago in Application 5 Unlikely to implement

Notify Coworkers that something changed in the Code

What is the challenge? I am working on an internal app together with a colleague. She was working on a feature, that had direct impact on the page that I was looking at. While I was using that page, she had Elle do some changes to the UI. My UI ve...
Guest about 2 months ago in Build 0 Future consideration

Use the record name by default for joined custom table records in reports

What is the challenge? When a custom table is added to a report through a join, the report currently shows the first available field by default instead of the field that best identifies the record. What is the impact? This can feel inconsistent...
Kate Mason 3 months ago in Custom tables 0 Future consideration

Complete Auto Import Functionality -- not just children of existing linked records

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...
Guest over 7 years ago in Jira 6 Future consideration

Allow hiding of statuses from Kanban views

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 ...
Guest 9 months ago in Features / Ideas 5 Future consideration

Extend or add search capability in archived workspace section

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...
Guest 9 months ago in Account settings 1 Future consideration

Add AI query and summarization tools to the backend of Aha! Knowledge for internal authoring

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 ...
Guest over 1 year ago in Knowledge bases 0 Future consideration

Handle multiple FixVersions in JIRA

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...
Danny Archer almost 11 years ago in Jira 17 Future consideration