Convert from integrations 1.0 to integrations 2.0

The new integrations 2.0 provides the most flexible and comprehensive integration capability between product roadmapping software and development systems ever available.

Integrations 2.0 includes a wealth of enhancements including the ability to:

  • Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link to nearly any development system record type.
  • Map any built-in or custom fields in Aha! to any similar field in your development system and specify which direction updates should flow between the systems.
  • Import your backlog directly from your development system to make getting started a smooth transition.
  • Automatically import new records created in your development system.

Integrations 2.0 currently supports:

  • Jira
  • Jira via Connect
  • Rally
  • GitHub
  • GitHub Enterprise
  • Visual Studio Team Services
  • Team Foundation Server

To streamline the process of moving to the 2.0 version, a Convert to Integrations 2.0 option is available under the More options dropdown for any 1.0 integration that has 2.0 support.

Aha-convert-integrations-1-to-2.png

How it works

Converting to a 2.0 integration is easy. All you need to do is go to your existing integration, click More options on the top-right corner of the integration's configuration page, and then select Convert to Integrations 2.0

After you click Convert to Integrations 2.0, you will be prompted to confirm your choice. You cannot convert back to a 1.0 integration, so it is important to be sure you want to convert prior to confirming the selection.

When you convert the integration, Aha! will transfer over the 1.0 integration's mappings to the 2.0 framework. 

Once the integration is converted, you will be directed to the 2.0 setup workflow and need to reauthenticate your integration.

After authenticating, you can proceed through the setup workflow to verify everything is configured as you would like, including the new field mapping options available in 2.0.

Converting for Jira integrations

Converting this integration will automatically migrate all linked records to Integrations 2.0 and apply the following to a new integration:

  • Project
  • Record mappings
  • Preferences for syncing tags
  • Preferences for sending releases

The following should be considered before converting:

  • The new integration will need to be authenticated. Be sure to have your Jira credentials available.
  • Some custom fields may need to be remapped. Please make note of any custom fields that are mapped in the existing integration.

Converting for Rally integrations

Converting this integration will automatically migrate all linked records to integrations 2.0 and apply the following to a new integration:

  • Workspace
  • Project
  • Record mappings
  • Preferences for syncing tags
  • Preferences for sending releases

The following should be considered before converting:

  • The new integration will need to be authenticated. Be sure to have your Rally credentials available.
  • Status mappings must be remapped. Please make note of status mappings in the existing integration. 

Converting for VSTS/TFS integrations

Converting this integration will automatically migrate all linked records to integrations 2.0 and apply the following to a new integration:

  • Project
  • Area
  • Record mappings
  • Status mappings
  • Default fields

The following should be considered before converting:

  • The new integration will need to be authenticated. Be sure to have your VSTS/TFS credentials available.

Converting for GitHub integrations

Converting this integration will automatically migrate all linked records to Integrations 2.0 and apply the following to a new integration:

  • Repository
  • Issue mappings
  • Preferences for syncing labels

The following should be considered before converting:

  • The new integration will need to be re-authenticated. Be sure to have your GitHub credentials available.
  • Status mappings must be remapped. Please make note of status mappings in the existing integration.

Mapping the Aha! URL field

In integrations 1.0, the URL for the Aha! record automatically populates in the development system. With integrations 2.0, this field needs to be manually mapped. The field to map from Aha! is called URL. The corresponding field that URL should map to depends on the development system. For example, in Jira, the field to map URL to is called Aha! Reference.

Templates

When you convert an integration template from 1.0 to 2.0, all integrations using that template will automatically convert over as well.

The template integration will take you into the above-described workflow, where you need to first reauthenticate and then proceed through the setup workflow to validate your configurations and enable the integration.

All other integrations using the template will also need to go through the setup workflow to validate configurations and enable the integration. However, the credentials will not need to be entered again. 

Webhooks for Jira integrations

Webhooks are used to communicate changes in Jira back to Aha! In most cases, a single webhook is needed to support every integration; adding multiple webhooks will cause problems and is not recommended.

The caveat to this comes when converting from 1.0 to 2.0. A webhook belonging to a 1.0 integration will only support Jira to Aha! communication for other 1.0 integrations. Similarly, a webhook for a 2.0 integration will only support communication for other 2.0 integrations.

If you convert all of your 1.0 integrations to 2.0, you have nothing to worry about. The webhook you had active previously will be transitioned over and will support your 2.0 integrations just like it did previously.

If you only convert some of your integrations over, you will need to ensure one of the converted integrations has its webhook added to Jira. Otherwise, your 2.0 integrations will not receive Jira updates. Similarly, if you convert the integration to 2.0 that had its webhook in use within Jira, you will need to add another webhook for your remaining 1.0 integrations.

 


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