Aha! Roadmaps | Integrate a single workspace with multiple projects from the same development tool

Most of the time, one integration links a single Aha! Roadmaps workspace to a single project in your third-party development tool of choice. However, there are a few scenarios where you may want multiple integrations for a single Aha! Roadmaps workspace.

Click any of the following links to skip ahead:

• When to do it

• Unique integration names

• Use integration templates

• Use custom fields

• Configuration

When to do it

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

1. Development tool 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 development tool projects.

2. Development tool projects may be set up by teams. If several teams are working towards a single release, multiple development tool 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 development tool integrations to different development tool instances would map to a single Aha! workspace.

Top

Unique integration names

When setting up multiple development tool integrations for a single Aha! Roadmaps workspace, it is important give each integration a unique name (something like "Jira - iOS team," or "Azure - North American team"). This allows you to see which development tool project you are sending your Aha! Roadmaps features to. To rename an integration, click on the integration title (named after the development tool 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 development tool instance. If you are using multiple 2.0 integrations with Jira or Rally, these templates can be leveraged to freely move records between projects and workspaces once you have met the prerequisites for moving records.

For integrations with on-premises tools like Jira Server or Azure DevOps 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 your development tool, open the Aha! Roadmaps record and use the Integrations dropdown on the Overview tab to Send to <development tool>.

Top

Use custom fields

If you are dividing a single release into multiple development tool 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 development tool project.

If a large team is releasing updates to several workspaces through one development tool project, multiple workspaces in Aha! Roadmaps would map to a single development tool project.

Top