ADD A NEW IDEA

Integrations

Showing 916 of 8640

SAP Cloud for Customer (C4C) CRM integration

Our company has recently transitioned from Salesforce to SAP C4C. In this, we have lost integration between our CRM tool and Aha. It would be great if there was a C4C <> Aha integration for cases as there is for Salesforce.
Daniel Scudds almost 5 years ago in Integrations 2 Future consideration

MS Planner integration

In our department we have developer teams working with Jira but also other teams for e.g. process improvements, consultancy... It makes no sense to track their work in Jira as they only need a simple board for their needs. Currently they use the M...
Guest almost 5 years ago in Wanted 8 Future consideration

Integration with Team Support

Provide integration between Team Support (enhancement requests) and Aha (Ideas).
Matthew Monahan almost 5 years ago in Integrations 0 Unlikely to implement

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 almost 5 years ago in Integrations / Wanted 3 Future consideration

Integration with Aha!

If one of my business partners used Aha! -- I'm trying to sell them on it -- it would be really cool, in theory, to be able to integrate with their instance. They currently use Pivotal Tracker and I integrate some features with them. If they moved...
Tom Beck almost 5 years ago in Wanted 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 almost 5 years ago in Azure DevOps Services and Server 0 Future consideration

The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.

Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet almost 5 years ago in Jira 1 Future consideration

Integration with ALM Octane

Micro Focus ALM Octane is a comprehensive lifecycle management solution that accelerates enterprise Agile transformations for high- quality application delivery at enterprise scale while leveraging existing investments. The flexible platform integ...
Guest almost 5 years ago in Integrations 0 Unlikely to implement

Trello Integration: Static string mapping

Hi, Trello Integration is already cool, we can flexibly map various Trello fields to various Aha fields, and for some fields also specify how particular Trello values map to particular Aha values. However, this still assumes that for every Aha f...
Guest about 5 years ago in Trello 0 Future consideration

Trello Integration: Specify target release

Hi, Currently, all Trello cards are automatically imported into the current release. That might not be always desirable. It would be helfpul if users could specify the Aha release into which the particular Trello integration would import.
Guest about 5 years ago in Trello 1 Future consideration