Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 943

Add ability to map Custom Aha! Tables to Jira

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

Include integration mapping details in integration reporting

We want to automate the documentation of all of our integration points (integration to Jira). We would like to see not only the integration name, rather we would like to see the specifics field mapping information , direction of integration etc...
Arieh Stroul 2 months ago in Integrations / Reports 0 Future consideration

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

In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! 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. ...
Danny Archer almost 7 years ago in Dependencies / Jira 3 Future consideration

Sync contact names in Salesforce integration

The names of the people we do business with is very important. The Salesforce integration should sync the contact names of our clients in Salesforce with the Ideas portal to enure consistancy and data consistancy.
Daniel Lynch about 3 years ago in Salesforce 0 Future consideration

When using Import Records, not retaining parent/child relationship (AzDo Integration)

Who would benefit? Aha users when setting up a new workspace What impact would it make? Improves ability to only bring in needed records How should it work? After setting up integration mappings with parent/child relationships, have import records...
Guest 9 months ago in Integrations 1 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 over 5 years ago in Azure DevOps Services and Server 1 Future consideration

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

Epic progress doesn't update when it has children in different projects

Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
Kyle d'Oliveira 10 months ago in Jira 0 Future consideration

Including Attachments from Comments for Jira Integration

It would be useful if we had the ability to push attachments made on comments, to Jira. Today, only direct attachments (to features or requirements) are supported, but from a UX perspective, attachment from comments should be included too, OR an a...
Reut Levi over 4 years ago in Integrations 3 Future consideration

Process for handling account merges in SFDC

What is the challenge? In Salesforce if I merge an account into another account any ideas that were linked on the source account are transferred over to the target account. On the Aha! side, the link in the proxy vote to the account still points b...
Justin Waldorf 7 months ago in Salesforce 0 Future consideration