ADD A NEW IDEA

Integrations

Showing 631

improved metadata rest services for fields

For users trying to interface with the Aha service via the rest services there is a definite lack of available services for fields. There needs to be a way to validate fields being sent to Aha. Currently there are only services that return filed ...
Tim McCaskill almost 5 years ago in Integrations 1 Future consideration

Allow for a check list to be copied to the GitHub product AND not change the check list in the originating work activity.

The check list (versus ordered / unordered list) in the text field is very nice. However, integration process translates the Check List to an unordered list in GitHub and then updates that back to the originating work activity. This process change...
Guest almost 5 years ago in GitHub 0 Future consideration

Automatically create webhooks by default for Azure/TFS

No description provided
Guest almost 5 years ago in Azure DevOps Services and Server 0 Future consideration

Associate an idea with a SalesForce Contact

Current Salesforce idea integration is only with Accounts, Cases and Opportunities. Would like to be able to associate with a contact
Guest almost 5 years ago in Salesforce 1 Future consideration

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

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 about 5 years ago in Jira 1 Future consideration