Skip to Main Content
ADD A NEW IDEA

My ideas: Integrations

Showing 647

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 7 years ago in Wanted 9 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 5 years ago in Azure DevOps Services and Server 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), each i...
Guest almost 5 years ago in Azure DevOps Services and Server 1 Future consideration

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 about 2 years ago in Integrations 0 Future consideration

Slack integration: Unfurl URLs for any record type

Currently we only unfurl records that you can create. We should unfurl any record when a URL us posted in Slack.
Austin Merritt 2 months ago in Integrations 0 Future consideration

Ability to import child records when connecting to an existing record in Jira

What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...
Nerissa Muijs 2 months ago in Jira 0 Future consideration

Allow for Lookup Fields to be mapped in SFDC integration

Who would benefit? Everyone What impact would it make? Allows for further data collection from SFDC in Aha! How should it work? Similar to how other SFDC fields are currently mapped in today's configuration.
Guest 5 months ago in Salesforce 0 Future consideration

Dovetail integration

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

Enhancement to custom fields for ADO integration

What is the challenge? Manual processes required What is the impact? Improve ability for automation Describe your idea "I have an ADO integration set up (one way) to allow me to raise requests to a team direct from Aha. However, they require a spe...
Ben Bulow 3 months ago in Integrations 0 Future consideration

View in Aha! the author of a comment created in Azure DevOps

In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
Guest about 3 years ago in Integrations 1 Future consideration