ADD A NEW IDEA

Integrations

Showing 631

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

Ideas integration with Gainsight CS

Our Support team uses Gainsight CS to track and manage interactions with customers. They want to be able to look at Aha ideas submitted, voted on, or subscribed to by specific customers all without leaving Gainsight. They will use this during cust...
Brian Trombley almost 4 years ago in Wanted 3 Future consideration

Target Process

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

Allow mapping to the Rally iteration field

There is a built-in Rally field named iteration. It would be useful in many situations to map the iteration field to an Aha! field.
Austin Merritt about 2 years ago in Rally 3 Future consideration

Sync the change of parent link made in Aha! across 2 Azure DevOps integrations

Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
Stuart Blair 2 months ago in Azure DevOps Services and Server 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 almost 9 years ago in Salesforce 10 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 6 years ago in Jira 3 Future consideration

Defect: Jira Integration record mapping doesn't use custom terminology

Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Guest 2 months ago in Jira 0 Future consideration

Allow project access token to be used instead of personal token for GitLab integration

Who would benefit? anyone using the integration with aha and GitLab What impact would it make? improves resiliency and stability of the integration How should it work? Currently, to set up the GitLab integration a user in GitLab must use a persona...
Guest 2 months ago in Integrations 0 Future consideration

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox about 3 years ago in Jira 0 Future consideration