ADD A NEW IDEA

Integrations

Showing 945

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

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 almost 10 years ago in Pivotal Tracker 4 Will not implement

Survey Monkey Integration

An integration to survey monkey would allow survey feedback from users to be feed straight in to Aha.
John M about 4 years ago in Integrations 0 Future consideration

Please Add a Setting to Turn Off the Automatic Imports of Unlinked Jira User Stories

I believe that the way integration is currently implemented is based on a faulty assumption, e.g. that customers want all user stories created in an integrated Jira project and board to be sync'd to Aha!. We'd much prefer that this not be the ca...
Doug Wilson over 4 years ago in Jira 1 Future consideration

Export Error Log File related to Integrations

Ability to export Error Log to CSV File
Josh Tambor over 4 years ago in Integrations 3 Future consideration

Sync Release Phase to Azure DevOps

We have adopted a SAFe framework where features are planned quarterly. As a result we are creating 'Releases' in Aha that are materializing these quarters. Within a quarter we may deploy the software multiple times and we are using release phases ...
Nicolas Andrillon almost 3 years ago in Azure DevOps Services and Server 0 Future consideration

Sync owner field from Aha! to Pivotal Tracker

Synchronisation of the owner field. Stories created in Pivotal Tracker should have the corresponding owner on the Pivotal Tracker side. That can be determined based on e-mail, your team confirmed that it is possible. Priority 2 of 4
Guest about 10 years ago in Pivotal Tracker 2 Will not implement

Include Investment Types for Release In Integration

What is the challenge? For Releases Investment types are not supported in Integration Set Up How would you solve it? Manually Project Managers are adding in Devops What impact would it make? It will reduce so much of manual work
Guest 7 months ago in Azure DevOps Services and Server 0 Future consideration