Integrations

Showing 957

Sync contact names in Salesforce integration

The names of the people we do business with is very important. The Salesforce integration should sync the contact names of our clients in Salesforce with the Ideas portal to enure consistancy and data consistancy.

Daniel Lynch over 3 years ago in Salesforce 0 Future consideration

3 VOTE

Adjust sync direction for URL fields in integration mappings

What is the challenge? When a URL custom field is referenced within field mappings of an integration, it can not be set to update from the integrated system to Aha! only from Aha! to the integrated system. What is the impact? We can not adjust dir...

Kristina Gass 7 months ago in Integrations 1 Future consideration

20 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 about 4 years ago in Jira 0 Future consideration

12 VOTE

Provide alternative way to match users when email address is not exposed in Jira

Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...

Madeleine Black over 2 years ago in Jira 1 Future consideration

27 VOTE

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 over 5 years ago in Azure DevOps Services and Server 1 Future consideration

28 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 almost 6 years ago in Azure DevOps Services and Server 0 Future consideration

15 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 about 3 years ago in Azure DevOps Services and Server 0 Future consideration

35 VOTE

Clubhouse integration

Clubhouse is gaining a full head of steam and being adopted widely as a replacement for Trello and Jira - it strikes a great balance between the two. We're currently evaluating a move from PivotalTracker to Clubhouse, and while we're excited by th...

Guest over 7 years ago in Wanted 9 Will not implement

1 VOTE

Update blank Jira fields on import to Aha! even if they are set up as a two-way sync

Currently only fields that are mapped one-way from Aha! to Jira will update when imported to Aha! - we import records from Jira to Aha! without a version set in Jira and Aha! automatically adds them to a default release in Aha! - we would like Aha...

Diane Metzger 3 months ago in Integrations 0 Future consideration

5 VOTE

Epic progress doesn't update when it has children in different projects

Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...

Kyle d'Oliveira about 1 year ago in Jira 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY