Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Pinned ideas

PINNED Chrome extension to capture feedback from anywhere
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

Showing 9810

Allow navigation to be customized depending on the user

Allow navigation to be customized depending on the users individually so that I can have only certain people allowed to see the more confusing aspects of the interface.
Guest almost 10 years ago in Account settings 3 Unlikely to implement

Show similar ideas on the research tab

It'd be really helpful to put a 'similar ideas' section on the new Research tab to help find other similar ideas you might have missed. Then there could be a 1-click promote button that would promote it to the current feature.
Todd Meyer over 2 years ago in Ideas / Ideas research 1 Future consideration

Add placeholder text to templates in the text editor

Aha! allows me to create templates for my features (and hopefully one day for notes). My feature templates often include instructions for users. I typically style this a certain way so the user knows it's just help text. It would be great if I cou...
Nathaniel Collum almost 5 years ago in Features 1 Future consideration

Shipped releases should be archivable

After a certain period of time, it is no longer helpful to see a release that has been shipped. It should be possible to "archive" a release so that it no longer is visible in dropdowns, the release list, or the feature board.
Guest about 11 years ago in Releases 1 Unlikely to implement

Ability to choose how each Aha Initiative/Feature/Requirement should be mapped to JIRA, as opposed to one mapping setting for an Aha product.

As a user, when creating a new Aha Initiative or Feature, I would like the ability to choose whether the Aha Initiative/Feature/Requirement should be mapped as a JIRA Epic, User Story, or Requirement, so that I can have more flexibility when creat...
Guest almost 10 years ago in  0 Unlikely to implement

Private Comments

I would like to be able to create comments on features, requirements, initiatives, etc. but have the option of those comments only being visible to myself. I will have discussion notes, code snips that relate to the feature/requirement but they ...
Guest almost 9 years ago in Features 1 Will not implement

Restrict license allocation to paid seat groups, not accounts

It's ridiculous to have "paid seat groups" and allocate those licenses to other psg's within the account. Licenses limits should be observed strictly within each psg. I've lost seats for my group without my consent simply because they've over-allo...
Guest over 2 years ago in Account settings 0 Future consideration

AHA! Should share a public version of its roadmap so that users can know what changes/features are planned and when they are planned for

There are plenty of features I wish AHA! would have, and when I look at the ideas portal, some of them say, "likely to implement". What does that mean in terms of timeline? How long of a roadmap does AHA keep? These questions could be answered if ...
Oleg Yazvin over 7 years ago in Application 0 Unlikely to implement

Manage notes via source control

My team is using notes in Aha! Develop to document parts of our application. We want to ensure the documentation stays up-to-date as code changes, so we'd like to manage note content via source control. Especially content like UML diagrams.
Jeff Tucker almost 4 years ago in Notes 0 Future consideration

Ability for Contributors to Add free seats only

We want to allow contributors to be able to add users as 'free seats' in the Menu: Info > Users. Use Case: A contributor clicks on 'User' button to select either A) an existing user or B) add a new user 'email' as a free seat
Mike Jacobson almost 4 years ago in Application 0 Unlikely to implement