Most Aha! Roadmaps users set up a one-to-one integration between their Aha! Roadmaps workspace and their development tools, but there are scenarios where you may choose to integrate Aha! Roadmaps with multiple development tools or multiple instances of the same development tool.
For most of this article, we will focus specifically on Jira projects, but as you will see, these steps apply to many other integrations.
Click any of the following features to skip ahead:
When to integrate this way
There could be many reasons why you need to integrate multiple development tools — or create multiple integrations for the same tool — with a single Aha! Roadmaps workspace.
Development teams might use different tools. For example, your design team might use Trello, and two development teams might use Jira and GitHub. In that case, individual Aha! Roadmaps features would need to flow to the different systems to make sure your strategy is connected to the different pieces of development.
Multiple teams may contribute to the same Aha! Roadmaps workspace. To use Jira as an example, if two teams are working towards a single release, both Jira projects would map to a single Aha! Roadmaps workspace. In some circumstances, a single workspace in Aha! Roadmaps 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! Roadmaps workspace.
Best practices
If you are managing multiple development integrations in a single workspace, follow these tips to keep the data flowing correctly.
Use integration templates. Integration 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 workspace once you have met the prerequisites for moving records.
Give each integration unique names. When setting up multiple Jira integrations for a single Aha! Roadmaps workspace, it is important to name each integration. This allows you to see which Jira project you are sending your Aha! Roadmaps 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.
Use custom fields to designate Aha! records appropriately. 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.
Send record updates manually: 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.
Aha! Roadmaps supports integrating one Aha! Roadmaps account to multiple Jira servers. If you would like to do this, please email support@aha.io 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.