What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...

With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), each i...

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.

We're going to start using Aha! on our product team, and we use Airtable for our dev tasks -- would be great to have the ability to connect items in here with tasks/projects/epics in Airtable.

While there's preliminary Zapier integration. IFTTT is a bit more accessible and flexible for most things.

You have Zapier integration which is basically the same, but we would rather use Microsoft flow... it cant be that hard once you have one to do another. Basically just requires you to apply and with your existing rest api's the rest will be fairly...

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

As a sw product manager in a 7.000 FTE company its highly important to be able to integrate between the two systems. The organization is about to start using Planview as our portfolio managment tool wheras our SW department have been using aha for...

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

ADO integrations are sending to legacy domain "https://fredwin.visualstudio.com" instead of sending to "https://dev.azure.com/fredwin". Though the integration works as expected, clicking the link to the integrated record sends to the incorrect dom...