Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 950 of 9044

Provide REST API Contract

The REST API docs should publish a Postman collection/OpenAPI specification to aid in developer understanding and help facilitate application integration.
Jeremy Royster almost 4 years ago in Integrations 3 Future consideration

Add status filter to Github importer

The importer shows all repository issues, including closed issues. It also doesn't show what the issue status is, so we must click through them to find those we want to import. I suggest: adding a status filter, set it to show open issues only sho...
Alexey Zimarev 7 months ago in GitHub 0 Future consideration

Integration with Zoho Desk

Integrate Aha! with Zoho Desk I would like to be able to push tickets from Zoho Desk that are feature requests, to Aha where they are managed by the product team. Currently, Zoho Desk customers can do a quick CONNECTION between Zoho Desk and...
Guest about 5 years ago in Integrations 3 Future consideration

CodeBeamer integration

A number of teams in my organisation use CodeBeamer to manage work. We'd like a two-way integration with CodeBeamer in line with Jira and DevOps.
Simone Bilton over 1 year ago in Integrations 1 Future consideration

Allow the use of "Integration" fields in Report calculated field formulas

Currently, integration fields like "Rally formatted_id" cannot be used within a formula for report calculated fields. This is limiting since it means we need to create a custom field to be based on these fields to use within the formulas. Consider...
Karla Johnson almost 3 years ago in Integrations 0 Future consideration

Support for Jira Code Markup

Need to support the Jira code markup option. If the developer enters sample code as part of the description in Jira, the description gets updated in Aha! However the code markup is translated into very large tables in Aha! At some point, Aha! upda...
Guest over 8 years ago in Jira 2 Future consideration

Allow requirements to be associated with the release record

The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
Guest about 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 almost 6 years ago in Azure DevOps Services and Server 7 Future consideration

Ability to Integrate Ideas with Jira Service Desk

What is the challenge? I am using a Jira Service Desk to capture new product and project requests and would like to use the Aha! Ideas for review and prioritization before sending to a specific Aha! Product Workspace. What is the impact? Today I h...
Matt L 7 months ago in Jira 0 Future consideration

Pivotal Tracker: Send releases to PT

We are currently using the Aha.io and pivotal tracker integration to help seed our product roadmap into the engineering team's workflow. This has been great so far but the one biggest points of friction is trying to keep track of the features that...
Suzanne Vaughan about 10 years ago in Pivotal Tracker 4 Will not implement