Create multiple development tool integrations for a single Aha! workspace

Coming soon: We are introducing a fresh new look for record drawer and details pages on September 30, 2020. This article describes the current experience. Preview the upcoming improvements in your account now so you can get familiar with the new way of working in Aha!

  • Switch to the new experience using a toggle in the More options button in the drawer of each record.
  • The toggle is unique to each user — so you can opt in and out as often as you like.
  • We also updated the application font in the new experience for improved text legibility.

Most Aha! users set up a one-to-one integration between their Aha! product and their development tools, but there are scenarios where you may choose to integrate Aha! with multiple development tools or multiple instances of the same development tool. 

  1. An Aha! product may require multiple development tool integrations if your design team uses Trello, and your two development team use Jira and GitHub, for example. In that case, individual features need to flow to the different systems to make sure your product strategy is connected to the different pieces of product development.
  2. Multiple teams may contribute to the same Aha! product. To use Jira as an example, if several teams are working towards a single release, multiple Jira projects would map to a single Aha! product. In some circumstances, a single product in Aha! is being contributed to by several teams (internal and contracted/outsourced teams). In this case, multiple Jira integrations to different Jira instances would map to a single Aha! product.

For the rest of this article, we will focus specifically on Jira projects, but as you will see, these steps apply to many other Aha! 2.0 integrations

When setting up multiple Jira integrations for a single Aha! product, it is important to name each integration. This allows you to see which Jira project you are sending your Aha! features to. To rename an integration, click on the integration title (named "Jira" by default) at the top of the integration configuration screen and type a unique identifier for the integration.

Integrations 1.0 templates and 2.0 templates save time when setting up multiple integrations to the same Jira instance. If you are using multiple 2.0 integrations with Jira, these templates can be leveraged to freely move records between projects and products once you have met the prerequisites for moving records.

When you are ready to send a release or individual features to Jira, select the specific Jira configuration to send to from the Actions drop down.

If you are dividing a single release into multiple Jira projects, add a tag or custom field to identify the project the feature relates to. Then you can easily use bulk edit functionality to send features to the relevant Jira project.


  • If a large team is releasing updates to several products through one Jira project, multiple products in Aha! would map to a single Jira project.
  • Aha! supports integrating one Aha! account to multiple Jira servers. If you would like to do this, please email and we will configure the account for you. 
  • While it is possible to send the same record through multiple integrations, we do not recommend it. For example, you may choose to send the same feature to your design team's Trello board and your development team's Jira project. This risks syncing errors between the three tools, and some fields do not allow for bidirectional updates.


Was this article helpful?
0 out of 0 found this helpful