ADD A NEW IDEA

Integrations

Showing 631

GitHub Integration: Aha! Release to Github Release mapping

As a product manager setting up my GitHub integration, I want to map Aha releases to GitHub releases directly, to avoid confusing developers and make Aha adoption less painful.
Guest about 5 years ago in GitHub 0 Future consideration

Add Ability to not send a specific release to Rally on Master Feature or Feature

Rally has a concept of Backlog where the Release is set as 'Unscheduled'. But there is no way in Aha! to assign a Master Feature or Feature to something like 'Unscheduled' so that the Release information does not get populated in Rally. We want to...
Amy Lackas about 5 years ago in Rally 0 Future consideration

Ability to map to "No entry" status in Rally

It is possible for a status in Rally to have a "No-Entry" value but you are not able to map to this in the integrations. In a use case where a record is created in Rally and does not have a status set (i.e. it is set to "No-Entry"), when you lin...
Madeleine Black about 5 years ago in Rally 0 Future consideration

For Jira integration, enable ability to prevent releases being automatically created in Jira (and/or enable this for releases in parking lot)

Right now we have an integration set up between Jira and Aha (which is extremely useful). However, whenever a feature in Aha that's linked to an issue in Jira has its release updated (e.g. moved from "v1.12.0" to "Backlog"), if the release to whic...
Guest about 5 years ago in Jira 0 Future consideration

Salesforce integration

The Google Analytics integration is great. It would be really nice to also have an integration Salesforce so we could track the leads generated from our various campaigns. For example, we send out an email campaign to a target audience. How many ...
Guest about 5 years ago in Salesforce 0 Future consideration

Map VSTS/TFS picklist custom fields to Aha! choice list fields

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Tessa Adair over 5 years ago in Azure DevOps Services and Server 9 Future consideration

Showcase Github Comments in Separate Thread

Our QA team has a hard time seeing the story of a ticket due to all of commit messages. It would be nice if instead of appearing as just comments the Github commits appeared separately or were able to be be filtered out.
Guest over 5 years ago in GitHub 0 Future consideration

Remove large delay (5m) from webhook calls.

Webhook callbacks have a delay that hinders a consistency of custom integrations. This delay, in addition to making the system less dynamic, makes it impossible to integrate more complex. A great example of webhook deployment is GitHub, which ma...
Guest over 5 years ago in Integrations 1 Future consideration

Add Product Prefix field as a choice in the JIRA integration

We integrate Aha! with multiple JIRA projects and often use the product prefix as the Component to identify the source of the ticket. Today we use a constant and add that manually. Adding it from the prefix would save us a lot of time!
Guest over 5 years ago in Jira 0 Future consideration

Ability to set Aha field to a constant value as part of integration field mappings

My scenario is that I have each Aha product linked to multiple different projects in Team Foundation Server (TFS), and I want the features in Aha that come from TFS to have a field indicating what TFS project they came from. But I can’t find a way...
Tessa Adair over 5 years ago in Azure DevOps Services and Server 7 Future consideration