Integrations

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.

Who would benefit? Anyone who manages an Aha board that syncs with Azure DevOps (ADO) What impact would it make? It would reduce out-of-date information in Aha & on roadmaps from records that rely on the ADO integration for updates. Additional...

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

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

Our customer facing teams use Gong and collect all kinds of great detail. If they could easily tag those meeting snippets and send to Aha it would make their submission of ideas with evidence that much more efficient.

It makes no sense that this isn't available today. All other idea submissions generate such notifications on status changes. This at least should be an option I can turn on when setting up the integration.

What is the challenge? Markdown editing has been added in Azure DevOps for rich text fields. However, when the data is migrated to Aha, it's stored as raw Markdown rather than displaying as formatted text. What is the impact? Makes integra...

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.

We are working integrations with some other systems, and the way part of it needs to be handled is via CSV file (Master Feature) - but Goal and Aha Score is not available for this import. This would be very helpful for our integration.

We are trying sync the Feature order from Aha to VSTS (never the other way around). Keeping the Features in VSTS in the same order in Aha is in our use case, critical to using the integration. The reason that it fails is because matching the Aha R...