Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 947

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

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

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 about 4 years ago in Rally 2 Future consideration

Ability to cancel background jobs

Who would benefit? all teams and aha What impact would it make? It would allow admins to stop a job from running such as an import when it is realized an integration was set up wrong etc. This will benefit aha because it will prevent unnecessary p...
Guest 9 months ago in Integrations 1 Future consideration

Show name of user whose token is being used in ADO integration

Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
Bonnie Trei about 1 year ago in Azure DevOps Services and Server 0 Future consideration

Integrate with Mural

Mural is a great visual management tool. Ideally Mural could be the foundation for the notes section in Aha!. Ideally....you could work on a Mural from within Aha!...so perhaps an integration of some sort. This allows for a virtual room where team...
Guest almost 7 years ago in Integrations 2 Unlikely to implement

Add better error handling for 'unhandled error exceptions'

When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...
Guest about 1 year ago in Jira 0 Future consideration

Allow additional Link Types in the 'Links to' field

Within AHA we are mapping Releases -> ADO Release Work Item Master Feature -> ADO Epics Features -> ADO Features. Master Features need to be located in the Release in which they complete. But Features (that contribute to this Master F...
Guest about 5 years ago in Azure DevOps Services and Server 2 Future consideration