Note: To keep from overloading third-party APIs, changes to the text editor and mockups are delayed by at least five minutes, waiting for five minutes after the most recent change.

Note: This article refers to features. Depending on your workspace type, you may see “activities" in your workspace.

Aha! Roadmaps | Integrate a single Aha! Roadmaps workspace with multiple Jira projects

Most of the time, one Jira integration links a single Jira project to a single Aha! Roadmaps workspace. However, there are a few scenarios where you may want multiple Jira integrations for a single Aha! Roadmaps workspace.

Note: The Jira integration is not the only one that supports this behavior. You can create multiple integrations for the same tool in a single Aha! Roadmaps workspace with any development tool.

Click any of the following links to skip ahead:

When to do it

These are the two most common reasons why you might want to configure multiple Jira integrations pointing toward multiple Jira projects in a single Aha! Roadmaps workspace.

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

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

Top

Unique integration names

When setting up multiple Jira integrations for a single Aha! Roadmaps workspace, it is important give each integration a unique name (something like "Jira — iOS team"). 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.

Top

Use integration templates

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 move records between projects and workspaces once you have met the prerequisites for moving records. For integrations with Jira Server, you can set the client certificate in the template, rather than setting it for each integration that uses the template.

When you are ready to send a release or individual features to Jira, open the Aha! Roadmaps record and use the Integrations dropdown on the Overview tab to Send to Jira.

Top

Use custom fields

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 workspaces through one Jira project, multiple workspaces in Aha! Roadmaps would map to a single Jira project.

Top

If you get stuck, please reach out to our Customer Success team. Our team is made up entirely of product experts and responds fast.

Aha! Roadmaps
    Strategic roadmaps
    Integrations
      Aha! Ideas
      Aha! Develop
      Announcements
      © 2021 Aha! Labs Inc.All rights reserved