Integrations

Showing 993 of 9642

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

15 VOTE

Jira integration user name

In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...

Karie Kelly over 3 years ago in Integrations 0 Future consideration

1 VOTE

Import numerical Jira scripted fields as Number custom fields rather than Text

What is the challenge? Currently, scripted fields generated in Jira, even if they are Number fields, can only be imported as Text custom fields in Aha. This means their numerical values cannot be treated as numbers, only as text. What is the...

Guest 3 months ago in Jira 0 Future consideration

5 VOTE

Record successful updates in Aha! from Jira "update records" action

What is the challenge? Currently, there are log events for successful updates made from Jira when using the "Update Records" action What is the impact? Users have no way of knowing which records were successfully updated and what fields were chang...

Stephanie Lechner about 1 year ago in Jira 0 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 about 6 years ago in Azure DevOps Services and Server 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 over 4 years ago in Jira 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 almost 8 years ago in Wanted 9 Will not implement

6 VOTE

Easily share relevant research documents on features through integration

What is the challenge? With the Research tab, many teams are creating documents to contain their research, technical requirements, and wireframes. But once I send a feature into Jira, I cannot pass along the relevant documents I want my engineerin...

Max Robbins over 1 year ago in Integrations 0 Future consideration

3 VOTE

Add ability to map Created by Field between Aha! and ADO Server accounts

What is the challenge? Currently there are a few user fields from ADO server accounts available to map to Aha!'s Created by User, but the Created By user is not displaying as an option. What is the impact? Users are unable to map the created by fi...

Stephanie Lechner 8 months ago in Azure DevOps Services and Server 0 Future consideration

45 VOTE

Add Salesforce integration to Salesforce custom objects

We use custom objects in our Salesforce org to track things like feature requests, bugs and other system support related issues. Allowing us to integrate Aha to a custom object would allow us to use the Aha integration with our existing org struct...

Guest over 10 years ago in Salesforce 3 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY