Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 949

Allow record mapping to Asana Projects

Asana best practices recommend projects represent distinct bodies of work with start and end dates. The Aha! integration requires, in the set up, selection of an Asana Project to connect the workspace to. This requires a new integration for every ...
Bonnie Trei over 2 years ago in Asana 0 Future consideration

Dovetail integration

Would love to see a dovetail integration so we can map UXR into our Aha Initiative, Epics, etc.
Guest over 1 year ago in Wanted 1 Future consideration

Including Attachments from Comments for Jira Integration

It would be useful if we had the ability to push attachments made on comments, to Jira. Today, only direct attachments (to features or requirements) are supported, but from a UX perspective, attachment from comments should be included too, OR an a...
Reut Levi over 4 years ago in Integrations 3 Future consideration

Improving handling when Jira users change issue type across record hierarchy

Who would benefit? Users of Jira integration What impact would it make? Users who are changing issue types in Jira after records are integrated. How should it work? Right now, if a Jira user changes an issue type on an integrated record, the integ...
Stephanie Lechner 12 months ago in Jira 0 Future consideration

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 almost 3 years ago in Salesforce 0 Future consideration

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 7 months ago in Integrations 1 Future consideration

JIRA: Detect default unit of time tracking

Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off. As of the 6.4.x version of the JIRA REST API a GET is available that ret...
Danny Archer about 9 years ago in Jira 12 Likely to implement

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

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

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 about 7 years ago in Wanted 9 Will not implement