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

Integrations

Showing 650

Include Area Path in VSTS Integration

I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
Guest over 7 years ago in Azure DevOps Services and Server 3 Future consideration

Choose the product on the integration with Zendesk

When you have multiple products in Zendesk it would be nice of you could select the product to link to by default, or change the order of the products in the drop down list. This prevents mistakes are made by the support agents.
Jeroen Geerbex over 10 years ago in Integrations 4 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

Link to Salesforce record through Aha

I understand it’s possible to link a Salesforce case, account, or opportunity to an Aha! Idea. It would be much more convenient to go the other way around so that you can link an Aha! Idea to Salesforce through Aha. That would prevent us from havi...
Guest about 8 years ago in Integrations 1 Future consideration

Ability to create JIRA integration thorough Aha API

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually
Guest over 8 years ago in Jira 3 Future consideration

Seamless Sync for Epics and Features Between Aha! and ADO when changing types

What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...
Rob Stebbens over 1 year ago in Azure DevOps Services and Server 1 Future consideration

Add a Qualtrics integration

We want to automate responses that come in from our NPS(Qualtrics) to flow into the VoC Ideas Portal (Aha).
Chelsea Carter over 2 years ago in Integrations 1 Future consideration

Change revision history descriptors for text field updates

It seems that some fields when updated via integration show a descriptor as XYZ changed integration link for Capability..123". This can be found in some values fields. Other fields like description simply state " XYZ updated the capability 123". T...
Karla Johnson over 3 years ago in Rally 1 Future consideration

Allow record mapping to Asana Projects

Asana best practices recommend projects represent distinct bodies of work with start and end dates. The Aha! integration requires, in the set up, selection of an Asana Project to connect the workspace to. This requires a new integration for every ...
Bonnie Trei almost 4 years ago in Asana 0 Future consideration

Sync releases for Azure DevOps integration

Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...
Ronnie Merkel over 5 years ago in Azure DevOps Services and Server 0 Future consideration