Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 946

New features created via an ADO integration are assigned to the parent epic release by default

Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
Bryan McElhinney over 2 years ago in Azure DevOps Services and Server 0 Future consideration

Support filtering in the API

The API pages the data it returns, and the pages are limited to a maximum of 200 records. In scenarios where it isn't possible to programmatically iterate through the pages, such as reporting & (Power)BI, it would be incredibly useful to be ab...
Daniel McGrath about 6 years ago in Integrations 1 Future consideration

Integration with Crayon Battlecards

It would be great to integrate Crayon into Aha so that we can have our competitor tabs populated with data from Crayon.
Guest over 4 years ago in Integrations 0 Future consideration

Support mapping tags to JIRA multicheckboxes

Problem Overview It is possible to bi-directionally map tags in Aha! with custom multicheckboxes in Jira. However, it is not possible to configure how the values should map on each side. This creates errors when the two fields attempt to sync. Pro...
Austin Merritt about 6 years ago in Jira 0 Future consideration

Event dimensions and metrics for GA integration

I was playing around with the GA integration for Aha for Product. It’s good but I noticed there weren’t any dimensions or metrics around event tracking. As a single page application we rely heavily on events and it would be great to be able to add...
Guest almost 6 years ago in Integrations 1 Future consideration

Include categories when importing from UserVoice

When importing a UserVoice forum, also import the categories, and link the categories to the imported ideas.
Chris Waters about 9 years ago in Integrations 0 Future consideration

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi over 8 years ago in Jira 11 Already exists

Map one Aha release to several Jira projects

We have several Jira projects aiming towards the same release. When importing fixVersions from several Jira project to one product in Aha we get one release for each project/integration in Aha. This means that if we have 10 projects aiming for the...
Guest over 6 years ago in Jira 0 Future consideration

Automatically send feature(s) to integrated system

As a product manager I want to have a feature I just created be automatically created in my integrated system, such as Jira. Adding a check box in the integration configuration for "Automatically send issue to integrated system" would be an easy w...
Guest over 6 years ago in Jira 5 Unlikely to implement

Update the Feature % Complete field based on User Stories of the DevOps Feature

Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
Guest almost 2 years ago in Azure DevOps Services and Server 2 Future consideration