Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 946

CSV import is frustratingly archaic

What is the challenge? importing data is slow and tedious What is the impact? customers will get frustrated and abandon Aha Describe your idea The import process should be improved and use a little bit of AI to better match existing fields with cu...
Guest 5 months ago in Integrations 0 Future consideration

Option to enable "bypassRules" for Azure DevOps integrations

What is the challenge? ADO projects can have work items rules in place that prevent the Aha integration from working. For example, the ADO state transitions may be restricted by values in other fields. What is the impact? In order to prevent the r...
David I. 5 months ago in Azure DevOps Services and Server 0 Future consideration

Slack support for portal comments

What is the challenge? Our team works primarily from slack so the more functionality provided within Slack without use of other tools is key for adoption. What is the impact? Describe your idea In this case, we have a slack channel set up to alert...
Keith Davenport 5 months ago in Slack 0 Future consideration

Allow To-Do's to be mapped to JIRA Issue Types

We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
Guest over 9 years ago in Jira 5 Unlikely to implement

Customise Aha! to Slack output

When, for example, an idea is created within aha! and the integration alerts a slack channel of this entry, it would be good to be able to customise the output of that notification and remove unwanted fields.
Guest almost 4 years ago in Slack 2 Likely to implement

Link idea and feature comments and other fields

I have set up Aha to integrate with Jira (development team) and Looper (field team), I would like to be able to have a seemless "automated" way to link comments and status between ideas and features. The idea being when Jira development teams have...
Chad Tidd over 4 years ago in Integrations 0 Future consideration

Allow editing to wiki-rendered fields in Jira

Who would benefit? Jira integration users What impact would it make? Currently Jira is sending broken formatting when fields leverage wiki-rendering with tables How should it work? If a user makes an edit to a table in Jira on a wiki-rendered fiel...
Stephanie Lechner about 1 year ago in Jira 1 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 over 6 years ago in Azure DevOps Services and Server 3 Future consideration

Work with Confluence for PRD Documents

Currently we use Confluence PRD documents: https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint It would be great if we could find some way to combine this with Aha. Otherwise, we spend time duplicating information from insi...
Guest over 9 years ago in Integrations 11 Already exists

Sync Idea categories to Salesforce

Who would benefit? Customer-facing teams (e.g. account managers) What impact would it make? It would allow team members primarily using Salesforce to pull reports on areas of the product that are important to the accounts/customers they manage. Ho...
Kellen Hawley about 1 year ago in Salesforce 0 Future consideration