Aha! Roadmaps | Integrate with Trello

Aha! Roadmaps provides a two-way integration with Trello that allows you to send your planned work from Aha! to your team working in Trello, and get progress updates back in Aha! Roadmaps in realtime.

You can also import your Trello data directly into Aha! Roadmaps through the Trello import.

Click any of the following links to skip ahead:

• Prerequisites

• Configuration

  • In Aha! Roadmaps

  • In Trello

  • Back in Aha!

• Configure mappings

• Enable the integration

• Add additional security

• Test the integration

Prerequisites

Top

Configuration

Before configuring any integration for the first time, it is important to fully understand how to think about integrating Aha! Roadmaps with your development tool.

To set up an integration with Trello, you need to be an owner in Aha! Roadmaps for the workspace you wish to integrate. You will also need to have a Trello account that has proper access to create/edit records in Trello for the board you plan to integrate with.

In Aha! Roadmaps

1. Navigate to Settings ⚙️ Workspace Integrations and click the + on the left side navigation bar. Select Trello from the integrations Task tracking category.

2. This will launch the integration configuration wizard. The first step is to name your integration and optionally select a template if you have already created one. Click Save and continue.

In Trello

1. Next, you will authenticate with Trello. After you click the Authenticate button, you will be taken to Trello to log in and grant Aha! Roadmaps access.

Back in Aha! Roadmaps

1. After authenticating, you will be prompted to choose a Trello board. You will be able to select from any of the boards that the authenticated Trello user has access to.

2. Next, you will be able to choose which list on the selected board new features get created in when they are sent from Aha! Roadmaps to Trello, and whether they should be added to the top or bottom of the list.

Top

Configure mappings

1. Next, you will configure how Aha! Roadmaps records are mapped to your Trello records. Initially, the mappings will be already set based on a standard configuration. However, you can also remove the default record mappings and add your own custom record mappings.

2. Click Field mapping to customize the field mappings for each record mapping. This is an advanced option within the configuration that allows you to customize how each field within the record is mapped between Aha! Roadmaps and Trello — as well as what relationship links exist for those records. The relationship links are important to consider because they establish the ability for records created in your development system to be automatically imported into Aha! Roadmaps in certain use cases.

   

3. While not every user will need to customize their field mapping, you do need to define the way Aha! Roadmaps statuses are mapped to Trello lists. Within the field mapping section for each Aha! Roadmaps record, there is a row for Status with a ⚙️ icon at the far right. Click the ⚙️ icon to open up the status mapping window. Matching values are automatically mapped initially, and then you can manually rearrange statuses to your preferred mappings as needed. Values may map one-to-one or one-to-many.

   

4. When mapping statuses, you will be presented with your Aha! Roadmaps status workflow for the record type on the left and your Trello lists on the right. You can drag and drop the statuses to create groupings and mappings.

Top

Enable the integration

With your records, field mappings, and statuses all set, you can click Save and continue to move onto the last step in the workflow. The Enable step allows you to specify how updates from Aha! Roadmaps are sent to your development system.

The default setting is: Automatically send outgoing changes, which means that any change made to an integrated record will send to Trello automatically.

We recommend the Approve outgoing changes setting for teams that are unfamiliar with how the integration works. The approval step allows teams that are new to the integration to validate what is being sent to their development system, which can help prevent unintentional changes from going through.

Note: If a feature's parent release is not linked with Aha! Roadmaps, or if releases are not mapped with the development system at all, then the feature will be imported into the first parking lot release. This is by design, since the parking lots are repositories for unscheduled work.

Top

Add additional security

2.0 integrations have the option to include a client certificate for added integration security. This can also be called mutual TLS (mTLS).

To set a client certificate, open your integration settings and click the More options icon in the upper right, then click Set client certificate. From here, enter the private key and certificate — we recommend creating a private key and client certificate specifically for this purpose — and click Save to save your changes.

If you use an integration template to manage multiple integrations in the same workspace, set the client certificate in your integration template. That way, you only need to set the client certificate once.

This feature will only provide additional security when the server that Aha! Roadmaps is communicating with validates the certificate. This is usually only possible with customer-configured on-premises integrations. Client certificate authentication is in addition to the standard username and password/token authentication and is not a replacement.

Top

Test the integration

Congratulations! You're ready to test your new integration. To do this, send a feature to Trello by following these steps:

1. Navigate to Features Board.

2. Click on a feature card, and select Integrations Send to Trello. A link to the Trello record should display in the Aha! Roadmaps feature after a few seconds. You can click on it to make sure that everything was sent to Trello correctly.

You can also bulk send a subset of features to Trello.

Top