To integrate Test Collab with Pivotal Tracker, you should have Pivotal Tracker API key ready with you.

Here are the steps to get your API key, in case you do not know:

  • Access the profile page after logging into Pivotal Tracker, 

  • On the profile page scroll to the bottom, here you should see your API TOKEN 

Configuring application wide integration settings for Pivotal Tracker in Test Collab:


Navigate to Main Dashboard > Settings > Issue Manager and provide the API key (in place of password) after selecting Pivotal Tracker from the drop down available on the issue manager integration settings page.


You can test the connection to the Pivotal Tracker instance by using the "Test" button.

You also have an option of allowing the reported issue to be resolved automatically when the related test case passes by checking "Resolve reported issues when a failed test case is marked as passed". When you check this you will be prompted to provide the status code that Pivotal Tracker uses for resolved issues, you need to enter the same for "Status code for resolved".

Project wise integration settings

When it comes to project wise settings for Pivotal Tracker, you will get the list of fields that are important for configuration. The list includes :


  • Project Id

  • Current State


For Project Id list of options will automatically be fetched from Pivotal Tracker on the basis of credentials provided by you during configuring application wide settings. For "Current State", you may provide any of the following values - 

  • accepted

  • delivered

  • finished

  • started

  • rejected

  • planned

  • unstarted

  • unscheduled


You can also add other fields including any custom field using "Add user defined field" from the drop down, clicking this you will get a text box in place of drop down to enter the name of the field.


A completed project specific issue manager setting form for Pivotal Tracker would look like this.



Once the values for all fields have been provided you can save and test the settings by creating a sample issue in Pivotal Tracker.


Did this answer your question?