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 9918

Ability to Hide Tab on Feature Cards

What: Hide Tabs on new look/feel experience for Feature Cards Why: Some information is more prevalent now in the view (e.g. Change Log) and may add confusion for our teams as we follow a different process for change management.
Guest over 5 years ago in Features 4 Future consideration

Allow inherited custom field layouts that can be extended for specific products

We would like to have a core set of common fields used in the field layouts for all products, but there will still be a need to support custom fields needed only by a subset of products. If we could have products inherit a custom field layout and ...
Guest about 8 years ago in Account settings 3 Future consideration

Allow Requirement Dates to drive that roll up to a Feature to drive that Feature's start & due date.

We integrate with Jira Engineering work at the Requirement level and must see dates associated with Jira Stories as Requirements in Aha! Since addressing the Requirements / Jira User Stories make our Features a reality, we request that a setting b...
Guest almost 8 years ago in Account settings 4 Unlikely to implement

ability to reference other fields within Aha record when using Draft with Ai

What is the challenge? When using draft with AI and basing the prompt on data that is already within Aha, it is necessary to have multiple windows or documents open in order to provide the prompt with the key points. What is the impact? The abilit...
Austin Wheat almost 2 years ago in Notes 2 Future consideration

Allow nesting of rollup releases

Rollup releases are very useful in organizations with complex and nested product lines and products. A top level product may have a V2.0 which is a rollup of three subsystems, a perfect use case of a rollup release. If each of the subsystems, in t...
Bastian Schoell almost 4 years ago in Releases 3 Future consideration

Ability to filter records in the ‘integration updates’ based on a field (eg: categories or tags)

Currently Integration update brings in all new records from Rally project. And there is no way to filter the data before import. Want the ability to filter on some Rally fields (eg. status & tags) which will help to import on the required reco...
Jyothirmayi Talaparthy over 5 years ago in Rally 4 Future consideration

Ability to report ideas by parent category

We need ability to show idea data based on high-level category. (ref attached picture) Every week I provide exec summaries to our product leadership who are only interested in data around the product at a high-level view. To accomplish this, I hav...
Laura Giles almost 6 years ago in Reports 1 Future consideration

Allow adding attachments in portal to any record you can edit

What is the challenge? Aha! user can update any idea in portal that they can view, but can only add attachments to ideas that they created. Portal user (or Aha! user) can update any proxy vote in portal that they can view (when portal settings all...
Jay Margolis over 1 year ago in Ideas portal 1 Future consideration

Allow mapping to the Rally iteration field

There is a built-in Rally field named iteration. It would be useful in many situations to map the iteration field to an Aha! field.
Austin Merritt almost 4 years ago in Rally 3 Future consideration

Ability to round percentages in charts

It would be useful to be able to specify the precision to which to display percentages in charts. I often don't need to know that something is 68.7375372...% I would like the ability to specify (at least) to what number of decimals to display on t...
Greg Horlacher over 4 years ago in Reports 4 Future consideration