How to think about integrating Aha! and your development system (integrations 2.0)

The majority of customers integrate Aha! with their development systems of choice. Aha! provides two-way integrations with a number of popular development systems, such as JIRA, Rally, Visual Studio Team Services, and many more.

When considering an integration between Aha! and your development system, it is very important to understand the intended workflow between the two systems.

Aha! is your planning tool. It is where product teams define strategy, organize their backlog, and prioritize work into releases to create their product roadmap. Development systems are for the execution of this work. They are where developers manage the task of implementing the planned features.

You plan before you work, and as such, Aha! is designed to come first in the process. Plan in Aha! and then utilize the integrations to send the planned work from Aha! to your development system for your team to build.

Integrations support the mapping of the following Aha! records to your integrated development system:

  • Initiatives
  • Master features
  • Features
  • Requirements
  • Releases

In addition to mapping the Aha! records to your development system, you also have flexibility to determine how the fields within the records map to corresponding fields in your development system — including the direction of the mappings.

Once the work has been sent from Aha!, a two-way link is established, allowing updates on either end to flow back and forth. As part of the integration configuration, you have the option to specify if outgoing changes from Aha! send automatically or require review prior to approval.

The overall workflow allows your product team to work in Aha! and your development team to work in their tool of choice — without requiring each team to go back and forth between systems.

How it works

First, you need to configure your integration. Each integration establishes a link between an Aha! product and a project space in your integrated system. You can also integrate a single Aha! product with the same system multiple times or integrate a single Aha! product with multiple different systems.

For details about configuration, please reference your system-specific support document here.

Once you have an integration configured and enabled, you will have the option to send releases, master features, and features from Aha! to your integrated system. The option will appear under each record's "Actions" menu, as shown in the screenshot below.



Once you send the record from Aha! to your development system, the integration for that record becomes active, allowing changes to sync back and forth based on how you have the integration configured. You will notice an integration link appear on the record, making it clear in Aha! which records are integrated and which are not.

Future updates from Aha! to your development system can be handled in one of two ways.

  1. You can opt to have all changes post to the integration updates window where your Aha! users can review changes prior to committing them to your development system.
  2. Or you can choose to automatically have changes in Aha! sent over, so that any time an integrated record changes, it automatically updates your development system.

Changes to integrated records coming from your development system into Aha! are handled separately. They are automatically imported as soon as the change happens. This is handled through adding an integration webhook in your development system.


In addition to sending outgoing changes and receiving updates to integrated records, you can also import new records that originated in your development system. The ability to import new records is based on parent-child relationships where the parent is sent from Aha! originally and then the child is added in the development system. This is very important to understand — Aha! is designed to come first in your workflow and the ability to import new records still adheres to that. 

An example of how this would work is:

  1. You send a release from Aha! to your development system.
  2. In your development system, you add the record type that you have mapped to an Aha! feature to the release created from Aha!
  3. That new record would appear in the import dialogue as a candidate to be imported due to the association with the release, which is a parent of a feature in Aha!


Was this article helpful?
3 out of 3 found this helpful
Have more questions? Submit a request

Roadmap software to manage your products.
Finally, connect strategy to execution.

Powered by Zendesk