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 983

Ability to create a report of integration errors across multiple workspaces

Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
Jor Bratko almost 4 years ago in Jira 6 Likely to implement

View in Aha! the author of a comment created in Azure DevOps

In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
Guest about 4 years ago in Integrations 1 Future consideration

Update records on all integrations linked to a template at one time

We anticipate having 150+ integrations based on a template (with the Rally integration). In order to add fields to the integrations, we edit the template and those updates/new fields flow to the individual integrations based on the template, howev...
Elaine Edwards over 5 years ago in Rally 2 Future consideration

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 about 7 years ago in Azure DevOps Services and Server 3 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 over 7 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 about 8 years ago in Jira 3 Future consideration

Integration with VersionOne

Bi-lateral sync with VersionOne
Guest over 8 years ago in Integrations 0 Unlikely to implement

Git commit messages separated from comments

Github integration messages in comments is great for smaller stories, but for anything non-trivial it becomes very easy to lose meaningful comments in the middle of a commit barrage. It would be very useful to have these either separated, or group...
Guest over 9 years ago in GitHub 1 Will not implement

Pivotal Tracker: Send releases to PT

We are currently using the Aha.io and pivotal tracker integration to help seed our product roadmap into the engineering team's workflow. This has been great so far but the one biggest points of friction is trying to keep track of the features that...
Suzanne Vaughan over 10 years ago in Pivotal Tracker 4 Will not implement

Sync owner field from Aha! to Pivotal Tracker

Synchronisation of the owner field. Stories created in Pivotal Tracker should have the corresponding owner on the Pivotal Tracker side. That can be determined based on e-mail, your team confirmed that it is possible. Priority 2 of 4
Guest almost 11 years ago in Pivotal Tracker 2 Will not implement