ADD A NEW IDEA

FILTER BY CATEGORY

Integrations

Showing 845 of 8098

Target Process

Integration with Target Process
Brian de Haaff about 8 years ago in Integrations / Wanted 12 Future consideration

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

In integrations 1.0 if I mappedFeatures = StoryRequirement = TaskAha! 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.In 2...
Danny Archer over 5 years ago in Jira 3 Future consideration

Account Admins have the ability to configure the account level Integration record mappings

Issue? The default Rally integration record mappings are Feature / Release / Requirement. Every new integration is being given the three record default which is confusing Aha users and enables users to deviate from the best practice of feature to ...
Mike Jacobson 4 months ago in Rally 0 Future consideration

Embed idea portal in salesforce community (replacing salesforce ideas)

Our support team is using salesforce ideas to gather suggestions, which is great, but i don't want to have manual entry to move ideas from there to AHA. Is there an option to integrate with Salesforce ideas? OR replace ideas by embedding an aha p...
Gord McNeill over 8 years ago in Salesforce 11 Future consideration

Add ability to map Custom Aha! Tables to Jira

Add the ability to map custom fields from custom tables in Aha! to Jira.
Guest about 6 years ago in Jira 5 Future consideration

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

Map Created By User from Jira

Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
Guest 10 months ago in Jira 1 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 almost 6 years ago in Wanted 9 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), ea...
Guest about 4 years ago in Azure DevOps Services and Server 1 Future consideration

Update the Feature % Complete field based on User Stories of the DevOps Feature

Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
Guest 9 months ago in Azure DevOps Services and Server 1 Future consideration