ADD A NEW IDEA

Integrations

Showing 918 of 8705

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 3 months ago in Integrations 0 Future consideration

Integration with Airtable

We're going to start using Aha! on our product team, and we use Airtable for our dev tasks -- would be great to have the ability to connect items in here with tasks/projects/epics in Airtable.
Guest over 5 years ago in Wanted 5 Future consideration

Integrate Aha! with Planview

As a sw product manager in a 7.000 FTE company its highly important to be able to integrate between the two systems. The organization is about to start using Planview as our portfolio managment tool wheras our SW department have been using aha for...
Guest about 5 years ago in Integrations / Wanted 3 Future consideration

Integrating with a specific Jira board

It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...
Reut Levi almost 2 years ago in Jira 1 Future consideration

Show name of user whose token is being used in ADO integration

Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
Bonnie Trei 8 months ago in Azure DevOps Services and Server 0 Future consideration

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

Integrate with Wrike

A lot of project management tools have bad road maps. Investigate those with bad road maps and attempt to integrate with the platform. There should be two options. Use the entire project as a road map or select one task and use the subtasks as ...
Guest over 6 years ago in Integrations / Wanted 5 Future consideration

Keep features in sync when they cross areas in Azure DevOps

This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
Deb Gay about 5 years ago in Azure DevOps Services and Server 0 Future consideration

Add Salesforce integration to Salesforce custom objects.

We use custom objects in our Salesforce org to track things like feature requests, bugs and other system support related issues. Allowing us to integrate Aha to a custom object would allow us to use the Aha integration with our existing org struct...
Guest about 9 years ago in Salesforce 3 Future consideration

Integrate ideas / epics with Rational Team Concert Work Items

Aha! currently integrates with other issue tracking systems just as Jira and Git Issues. Provide similar linkage with RTC work items.
Guest over 7 years ago in Integrations 4 Future consideration