Share your product feedback

ADD A NEW IDEA

Integrations

Showing 942

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 almost 6 years ago in Azure DevOps Services and Server 9 Future consideration

IFTTT Integration

While there's preliminary Zapier integration. IFTTT is a bit more accessible and flexible for most things.
Guest almost 10 years ago in Integrations 2 Unlikely to implement

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 over 5 years ago in Azure DevOps Services and Server 0 Future consideration

Integration with Microsoft Flow

You have Zapier integration which is basically the same, but we would rather use Microsoft flow... it cant be that hard once you have one to do another. Basically just requires you to apply and with your existing rest api's the rest will be fairly...
Guest over 8 years ago in Wanted 2 Unlikely to implement

Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations

With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), each i...
Guest over 5 years ago in Azure DevOps Services and Server 1 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 almost 6 years ago in Wanted 5 Future consideration

Azure DevOps Integration - Sync dependencies at UserStories/Requirements level

What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...
Guest 7 months ago in Azure DevOps Services and Server 0 Future consideration

Allow To-Do's to be mapped to JIRA Issue Types

We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
Guest over 9 years ago in Jira 5 Unlikely to implement

Work with Confluence for PRD Documents

Currently we use Confluence PRD documents: https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint It would be great if we could find some way to combine this with Aha. Otherwise, we spend time duplicating information from insi...
Guest over 9 years ago in Integrations 11 Already exists

Make the standard tags field mappable for requirements

Both epics and features have the standard tags field mappable when setting up an integration. Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created ...
Justin Waldorf over 2 years ago in Integrations 3 Future consideration
Idea management by Aha!
Create your own ideas portal to crowdsource feedback
© 2024 Aha! Labs Inc.•All rights reserved