Skip to Main Content

My ideas: Integrations

Showing 924 of 8731

Allow TFS integration to map bidirectionally for fields that are not in a built-in System.State.

Currently, the TFS integration does not support mapping arbitrary string fields to the Aha! workflow status field in a bi-directional way. Only the built-in System.State field in TFS can be mapped bidirectionally.
Guest about 4 years ago in Azure DevOps Services and Server 2 Future consideration

Add API endpoint to capture configuration details (custom fields, layouts, etc.)

Useful for external visibility of configuration, change tracking, automated configuration of external integrations making use of the data, etc.
Guest about 4 years ago in Wanted 0 Future consideration

Support 2 factor auth integration with Github

If you add Github Issues integration with a Github account that requires 2-factor authentication, the integration fails. It would be good to support this.
Guest over 8 years ago in GitHub 1 Already exists

Release Should Be Marked as Shipped only when all Integrations for JIRA projects are shipped

If multiple integrations are enabled at release level, allow workflow rule for release to be considered as shipped when all integrated JIRA projects have shipped the release If someone marks the release as shipped in JIRA, its changing the status ...
Amish Singhal about 4 years ago in Integrations 0 Unlikely to implement

Limit amount of text that can be input in a custom field

Set a max for the amount of text that can be added in a custom field (i.e max 50 words)
Mary D over 4 years ago in Wanted 0 Future consideration

Map user profile pictures from Salesforce community to Aha Ideas portal!

We want a seamless experience for our customers that are logged into our Salesforce community. Users have the ability to set their avatars in the Salesforce community but when they flow into the Aha ideas portal their avatar is not transferred ove...
Andrew C over 8 years ago in Salesforce 0 Unlikely to implement

Make fixed workflow transition enforcement optional for Jira integratations

Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it. With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need...
Daniel Hirschberg over 4 years ago in Jira 0 Future consideration

Pull in competitor information from Crunchbase

Reduce the tediousness of having to input competitor info manually
Guest over 4 years ago in Integrations 0 Future consideration

Change Button Click to Dropdown for Integration Screen

When completing the Integration, a user is asked to click through the various buttons showing the direction of the integration. A user has to make several button clicks to change the option, which is not always convenient. A drop down menu would b...
Josh Tambor over 4 years ago in Jira 0 Future consideration

Features assuming the same release as its parent master feature when importing from Jira

Given that I have an epic in Jira, linked to a Master Feature in Aha And the Master Feature is found in "Release X", When I create a story beneath that epic in Jira, Then the story should be imported as a child to the Master Feature, AND ass...
Guest over 4 years ago in Jira 0 Future consideration