ADD A NEW IDEA

Integrations

Showing 946

Bulk Action to delete integration link

Related to: https://big.ideas.aha.io/ideas/APP-I-2911. It would be great to have the option to bulk delete integration links for features in Aha. For example when you know the corresponding issues in JIRA don't exist anymore.
Marvin van Dongen about 8 years ago in Features / Integrations 5 Future consideration

Integrations 2.0: Add dependency link to connect records without natural relationships together

In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
Danny Archer almost 7 years ago in Dependencies / Jira 3 Future consideration

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

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

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

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

To Provide a search bar in Integration update page to search for records.

What is the challenge? Currently when we navigate to Integration updates to import any record which we need we need to manually navigate to multiple pages for accessing the required record to map with Aha! What is the impact? When the list of impo...
Guest 2 months ago in Integrations 0 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 over 2 years ago in Azure DevOps Services and Server 0 Future consideration

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

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 Future consideration