Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 923 of 8723

Do not allow requirements to be mapped without a Links To relationship set

It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
Madeleine Black over 1 year ago in Jira 0 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

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 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

Include Investment Types for Release In Integration

What is the challenge? For Releases Investment types are not supported in Integration Set Up How would you solve it? Manually Project Managers are adding in Devops What impact would it make? It will reduce so much of manual work
Guest 3 months ago in Azure DevOps Services and Server 0 Future consideration

Include Attachment for Release In Integration

What is the challenge? For Releases Attachments are not supported in Integration Set Up How would you solve it? Manually Project Managers are uploading in Devops What impact would it make? It will reduce so much of manual work
Guest 3 months ago in Azure DevOps Services and Server 0 Future consideration

Include Attachment for Release In Integration

What is the challenge? For Releases Attachments are not supported in Integration Set Up How would you solve it? Manually Project Managers are uploading in Devops What impact would it make? It will reduce so much of manual work
Guest 3 months ago in Azure DevOps Services and Server 0 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

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

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