ADD A NEW IDEA

My ideas: Integrations

Showing 937

Support mapping Asset object fields through Jira integration

Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
Stephanie Lechner 7 months ago in Jira 0 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 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: 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 almost 9 years ago in Jira 12 Likely to implement

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

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

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

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

Gitlab - Connect Master Features to Epics, and more

As one more request to improve connection between Aha and Gitlab :) We need better integration between Master Feature, Features and Requirements of Aha to Epics and Issues of Gitlab. A sample could be Master Features -> Epics and Features/Requi...
Fabio Brito almost 4 years ago in Integrations 3 Future consideration