Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 607

Warn user of integration on epic deletion

Who would benefit? Integration users What impact would it make? How should it work? When you delete a feature which is linked to a dev system you get a warning (attached). When you delete an epic, you do not get a consitent warning. This suggestio...
Tom Bailey about 1 year ago in Azure DevOps Services and Server 0 Future consideration

Group Level integration in Aha.

Who would benefit? All the teams who are using aha and Gitlab setup for their SAFe ways of working What impact would it make? Streamlined and logical grouping of features which are created in aha and synced to Gitlab How should it work? Group leve...
Anusha Huddar about 1 year ago in Features / Integrations 0 Future consideration

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

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

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

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

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

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

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