Integrate a single Aha! product with multiple Jira projects

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.

Although most Aha! users set up a one-to-one mapping between Jira projects and Aha! products, there are a few scenarios where multiple Jira integrations may be required for a single product.

  1. Jira projects may be set up for each individual codebase. If a single product is available on multiple platforms (web, iOS, Android, etc.), a single product in Aha! would map to multiple Jira projects.
  2. Jira projects may be set up by teams. 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.

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.

Note: 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.

Note: 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. 


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