Integrations

Showing 607

Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations

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

Guest about 5 years ago in Azure DevOps Services and Server 1 Future consideration

14 VOTE

Add support to map Azure Boolean Fields to Aha

This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...

Jerrold Emery almost 3 years ago in Azure DevOps Services and Server 0 Future consideration

3 VOTE

Prevent duplicate comments from importing into Aha!

What is the challenge? When re-syncing your integration from Settings -> Workspace-> Update records, duplicate comments can appear on the record in Aha! When a comment is edited in the inegration tool an additional comment with the edited co...

Gabrielle DeWitt 8 months ago in Integrations 1 Future consideration

18 VOTE

Support the ability to change a Jira project key

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.

Wayland Fox over 3 years ago in Jira 0 Future consideration

6 VOTE

Keeping link to Jira when disable an integration

When we disable an integration to Jira, we mean it to be we have a new Jira project to integrate to. It makes it easier on the integration on the feature to not have a huge list of Jira projects to integrate to and only to the projects that are ac...

Carina Velazquez about 1 year ago in Integrations 2 Future consideration

28 VOTE

Map VSTS/TFS picklist custom fields to Aha! choice list fields

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.

Tessa Adair almost 6 years ago in Azure DevOps Services and Server 9 Future consideration

26 VOTE

Keep features in sync when they cross areas in Azure DevOps

This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...

Deb Gay over 5 years ago in Azure DevOps Services and Server 0 Future consideration

12 VOTE

Allow mapping to the Rally iteration field

There is a built-in Rally field named iteration. It would be useful in many situations to map the iteration field to an Aha! field.

Austin Merritt over 2 years ago in Rally 3 Future consideration

16 VOTE

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 over 3 years ago in Integrations 1 Future consideration

1 VOTE

Webhook for integration log errors

I'd like an option to create a webhook that will send me messages when integration errors occur. I will use this webhook to create messages in Teams, so I know that I should go to either Aha or the source system to fix the issue.

David I. 3 months ago in Integrations 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY