Integrate Aha! with Pivotal Tracker

This two-way status integration allows you to push your completed features and requirements in Aha! into Pivotal Tracker and get status updates back. The integration supports both on-demand and private cloud versions of Pivotal Tracker.

When you have completed your product roadmap and feature planning, you can move features into Pivotal Tracker for the engineering team to work on. You can send them individually or in bulk for a release. This makes it easy for product management to set brilliant product strategy and share visual roadmaps while engineering can continue to work in Pivotal Tracker. Because of the two-way integration, status updates and changes to the story name and description are reflected in Aha! and the PM is able to automatically track what stories have been completed. 

You may also have a need to create multiple integrations per product in order to accommodate how the engineering team is split up. For example, you may have an overarching product to manage, but there may be two teams, one for the front end and one for the back end. This can be done simply by creating multiple integrations within Aha! Make sure you rename them on the top-left to keep the teams straight.

All integrations are configured in Settings > ProductYou need to be a Product Owner in Aha! and a project owner in Pivotal Tracker to set up this integration.


From Aha! to Pivotal Tracker

The following information is copied from Aha! when a feature is sent to Pivotal Tracker: 

  • Feature name
  • Feature description
  • Requirements
  • Attachments
  • Story point estimates

Feature details

  • One Aha! product is associated with one or more Pivotal Tracker projects.
  • Individual features can be sent to Pivotal Tracker using the Send dropdown on the features page.
  • All features in a release (that have not already been implemented or sent to Pivotal Tracker previously) can be sent to Pivotal Tracker using the Send dropdown on the release page.
  • Features can be mapped to epics or stories in Pivotal Tracker.
  • Requirements, which live in features, can be mapped to stories or tasks in Pivotal Tracker. 
  • Only the description and attachments of a feature or requirement are sent. No Aha! to-dos or comments are included.
  • When a feature is sent to Pivotal Tracker, its status in Aha! is automatically changed to "Ready to develop."
  • After a feature is first sent to Pivotal Tracker, changes to the name, description, and requirements can also be sent to Pivotal Tracker using the Update pivotal tracker option within the Send dropdown on the features page or by sending all features in a release to Pivotal Tracker again. New requirements will also be created in Pivotal Tracker, however, stories that were created for an existing requirement are not deleted from Pivotal Tracker if the requirement is deleted from Aha! If an attachment is deleted in Aha!, the corresponding attachment in Pivotal Tracker is not deleted.

From Pivotal Tracker to Aha!

Changes in Pivotal Tracker will be reflected in Aha! in real time. This enables the PM to be able to track what stories have been completed automatically. 

  • Story name
  • Story description
  • Story or task status
  • Story point estimates

Integration instructions

You need to be a Product Owner in Aha! and a project owner in Pivotal Tracker to set up this integration.

Please carefully follow these instructions to ensure that the integration is properly configured. These instructions are also found in Aha! under within the integration configuration page in your Product settings.

First, configure Pivotal Tracker:

  1. Go to the Settings page for the project, and then choose the Integrations tab or choose Configure Integrations.
  2. Under External Tool Integrations at the bottom of the page, create a new Other integration.
  3. Name the integration "Aha!" and set the Base URL to "https://<yourdomain>" (where <yourdomain> is the sub-domain for your account).
  4. Mark the integration as Active, leave the other fields blank, and save the integration.
  5. On the Profile page, copy the API token.

Next, create the integration in Aha!

  1. Navigate to the product you wish to integrate using the product dropdown to the right of your home icon.
  2. Under Settings > Product click on the + icon next to Integrations.
  3. Select Pivotal Tracker.
  4. Enter your API host for your private cloud, on-premise Pivotal Tracker. If you are using on-demand Pivotal Tracker, leave this field blank.
  5. Enter the API token you copied from Pivotal Tracker. Click the Test connection button. After a short delay, you will be able to choose the project the stories will be created in.
  6. Choose the integration in Pivotal Tracker that you created previously.

Finally, create a webhook

  1. Create a new Activity Webhook for v5 in Pivotal Tracker and paste in the Hook URL.
  2. Enable the integration.

Test the integration by going to one of your features in Aha! and using the Send dropdown on the features page. You should then look at your project in Pivotal Tracker and see that the feature (and any requirements) were properly copied.

Note: You can add the integration multiple times if you want to integrate multiple projects with a single Aha! product. Once you have added an integration, you may change the title to specify the project this integration belongs to by clicking on the title at the top of the integration setup page.

Configuration mappings

You can choose to send initiatives, features, and requirements over as follows:

  • Feature → Story, Requirement → Story
  • Feature → Epic, Requirement → Story
  • Feature → Story, Requirement → Task
  • Initiative → Epic, Feature → Story, Requirement → Task

You may also map feature statuses and feature types between Aha! and Pivotal Tracker. 



To help you troubleshoot any errors, we provide the detailed integration logs below. Contact us at if you need further help.

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