Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 947

Show custom field names on integration errors

When there's an integration sync error with Jira on a custom field, Aha shows something like this: 'customfield_19011': Please fill out required fields The identifier 19011 has no meaning to us, as Aha doesn't expose a mapping of our custom field ...
Brian Trombley over 3 years ago in Jira 1 Future consideration

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 11 months ago in Jira 0 Future consideration

Microsoft Dynamics CRM Integration

Would allow us to point roadmaps and other efforts to market opportunities that we track within CRM....
Steve Strickland almost 10 years ago in Integrations 6 Future consideration

To Provide a search bar in Integration update page to search for records.

What is the challenge? Currently when we navigate to Integration updates to import any record which we need we need to manually navigate to multiple pages for accessing the required record to map with Aha! What is the impact? When the list of impo...
Guest 4 months ago in Integrations 0 Future consideration

Salesforce Integration - Value field - Needs to pull in currency from SFDC to Aha

Currently the Amount field in SFDC on an opportunity transfers over to Aha when an idea is created from the opportunity. However, no currency goes with it. We are an international company and so we use multi-currency. The value field in AHA isnt p...
Guest over 3 years ago in Salesforce 3 Future consideration

Use Custom Table data in Integration with Jira

Need to functionality to include Custom Table fields in the integration mapping. We created a new table for Aha Roadmaps for Program Increments. The table is linked to both Epics and Features, to simplify the reports (same value for both). The cha...
Edgar Holguin over 1 year ago in Jira 0 Future consideration

Sync releases for Azure DevOps integration

Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...
Ronnie Merkel about 4 years ago in Azure DevOps Services and Server 0 Future consideration

Integration with Microsoft Flow

You have Zapier integration which is basically the same, but we would rather use Microsoft flow... it cant be that hard once you have one to do another. Basically just requires you to apply and with your existing rest api's the rest will be fairly...
Guest about 8 years ago in Wanted 2 Unlikely to implement

Map to a persona name value in integrations

Right now we leverage personas to describe who a release is targeting, where we'd love to be able to push the text value into our JIRA mapping
Barnett Klane about 5 years ago in Jira 3 Future consideration

Product Line initiatives linked back to Jira Epic

We have the following workspace hierarchy; Product Line A Product B Product C Each Product is setup to integrate with a different Jira Project. If I create a feature in Product C and link it to an initiative in Product Line A, the following happen...
Bill Simakis over 4 years ago in Jira 1 Future consideration