Integrate Aha! with Azure DevOps Services (integrations 1.0)

This support article refers to the historical 1.0 version of the Aha! integration with Azure DevOps Services. If you are looking for details about how to setup the Azure DevOps Services 2.0 integration, reference this article.

How it Works

This two way integration allows you to push features and requirements from Aha! into Microsoft Azure DevOps Services and receive updates back in Aha! from Azure DevOps Services. Azure DevOps Services may also be referred to as its old branding, Visual Studio Team Services (VSTS).

As with any Aha! and development tool integration, it is important to understand that Aha! comes first in the process. You plan, strategize, and complete work in Aha! and then send features and releases from Aha! to your development tool.



  • One Aha! product is associated with one Azure DevOps Services project.
  • A feature can be sent to the Azure DevOps Services server using the Actions > Send to Azure DevOps Services menu on the features page.
  • Requirements are sent to Azure DevOps Services together with the feature.
  • Only the name, description and attachments of features and requirements are sent to Azure DevOps Services.
  • If you set up a subscription in Azure DevOps Services, the integration can receive updates about name changes, description changes or status changes from Azure DevOps Services.
  • The mapping of Azure DevOps Services states to Aha! workflow statuses is configurable.


You need to be a product owner in Aha! to set up this integration.

Step 1: To configure this integration, first configure your Azure DevOps Services account.

  1. Open your account dropdown (usually identified by your first initial or profile image) in the top right of the page and choose the Security.
  2. Select Alternate authentication credentials.
  3. Check the box next to Enable alternate authentication credentials.
  4. Add a User name (secondary) and a Password. This credential will be used with Aha! (not your normal login credential).

Note: Ignore the warning about using personal tokens. You need alternate credentials. 

Step 2: Create the integration in Aha!

  1. Navigate to Settings ⚙️> Workspace and click the + button next to Integrations.
  2. Click on Azure DevOps Services.
  3. Enter the account name of your Azure DevOps Services account.
  4. Enter the Alternate Authentication Credentials you created in Azure DevOps Services.
  5. Click the Test connection button.
  6. On success, you should be able to choose a project from Azure DevOps Services. You also must select an area of this project where features and requirements should be created.
  7. Select the workitemtype to which features should be mapped. Then select for each Azure DevOps Services state to which Aha! workflow status it should be mapped. You may also indicate default values for fields that are required in Azure DevOps Services but not entered in Aha! under Default feature fields.
  8. Repeat step 7 for requirements.
  9. Enable the integration and test it by going to one of your features in Aha! and using the Actions > Send to Azure DevOps Services menu.
  10. The feature should now appear in your Azure DevOps Services project together with its requirements.

Step 3: Setup a subscription to receive updates from Azure DevOps Services

  1. Copy the webhook URL from the configuration page.
  2. In your Azure DevOps Services account, go to the project you want to integrate with.
  3. Click the small cog in the top center of the main navigation menu and click on the Service Hooks option.
  4. Add a new service hook by clicking the + button to create a new subscription.
  5. Scroll to and select the option for the Web Hooks service and click Next.
  6. Under the Trigger on this type of event dropdown choose the Work item updated trigger from the dropdown menu. You can leave the filters unchanged and click Next.
  7. In Action > Settings, paste the webhook URL from Aha! into the URL field. You can leave the option fields unchanged and click Finish to create the subscription.

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