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

Release--Progress-- Additional Customization

I would like the option to customize this perspective more and make it more presentation worthy. Right now it is pretty static.
Guest over 2 years ago in Presentations 0 Future consideration

Workspace Settings Report: Ability to group pivot table data by workspace settings fields

We have a large number of workspace layouts in use across the organisation. We'd like to be able to create a report that helps us to understand which settings are in use, where. A pivot report is ideal for this because we should be able to group w...
Guest over 2 years ago in Reports 0 Future consideration

Hide epic reference ID when showing related epics for your feature cards

When displaying epics related to features on the Features (release) board, I would like the ability to remove the epic ID so that only the epic Name is displayed. I use them as visual groupings of features and don't want additional "noise" on the ...
Guest over 5 years ago in Releases 0 Future consideration

When entering a tag and it makes suggestions - hitting enter should add first tag, not add a new unfinished word

Currently if you hit enter as the tag suggestions are displayed, it will enter a new unfinished word. This leads to messiness and tag cleanup.
Suzanne Vaughan over 10 years ago in Account settings 0 Already exists

In workflows, add the ability to limit setting a certain status to certain users.

In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless. If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets v...
Guest over 10 years ago in Account settings 2 Unlikely to implement

Ability to update Requirement or other record fields based on a query

We use a series of standard Requirements for each feature flowing through the pipeline. Depending on the values in certain fields, some of those requirements are not applicable. Automation lets me change the value of the workflow status, for examp...
Guest over 2 years ago in Features 0 Future consideration

A way to group specific status into one, and report on it

I am trying to create a ‘splash’ for our customers before they log into our idea site. I want to play up the ideas that they have entered, and how many of these ideas were actually developed. A ‘hey! Look what we have done based on your suggestion...
Guest about 8 years ago in Reports 0 Already exists

Allow integration with custom work item types

Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...
Guest over 5 years ago in Azure DevOps Services and Server 3 Already exists

Features should Inherit initiatives from Release & Master Release so all Pivotal stories are under the Epic after sending to PT (and the Epic is actually created)

When pushing a feature to Pivotal Tracker, a user can select a mapping that allows for initiatives to be mapped to epics. The only initiatives this works for are initiatives directly referenced by a Feature. Any initiatives referenced by the Relea...
Guest over 10 years ago in Pivotal Tracker 7 Unlikely to implement

Copy or share Initiatives between Products/Product Llines

In a product line with heavy integration between products, it would be helpful to be able to copy or share Initiatives between products.
Guest over 10 years ago in Strategy 0 Unlikely to implement