Integrations overview

Tracker has integrations with many popular tools such as GitHub, BitBucket, GitLab and Slack, as well as defect-tracking systems and customer support apps like Bugzilla, JIRA, and Zendesk. Additionally, we support integrations with the popular CI/CD pipeline solutions Concourse and Jenkins, as well as a custom form that allows you to add any CI/CD tool of your choice.

Integrations created by third-parties can be found on our Tracker Integrations page.

Tracker can also publish activity in your project to a Campfire chatroom or a custom application that listens to HTTP requests. You can create other integrations in any project you own that allow you to import from and link to Tracker stories, to tickets or issues in external bug tracking, or to customer support applications. You can also associate your source code commits with stories and update story state automatically via special commit message syntax.

You may need to open up your firewall to allow incoming requests from Tracker integrations (e.g., if you have an internal JIRA instance). If you need this, ask your network administrator to allow the IP addresses for the following:

• app01.pivotaltracker.com

• app02.pivotaltracker.com

However, please note that the IPs assigned to these addresses may change without notice.

Setting up an external tool integration

Your team can use Tracker to prioritize and collaborate around stories that are linked to issues/tickets in other systems (e.g., bug-tracking applications, customer support ticket systems, etc.). You can find more detailed setup information for each external tool integration in that specific tool’s Help Center article. However, in general, creating an integration will require the following steps:

1. Click the INTEGRATIONS tab in your project view.

2. Click the Add an integration button and select the type of integration you’d like to add.

3. Configure the integration. Most will require some form of user credentials, location/URL information, and possibly the ID of a saved search or a filter.

4. After you create an integration, you should see a new option in your project’s sidebar with the name you gave your integration.

5. Click on the integration name from the sidebar. If you’ve configured the integration properly, when you open the Integrations panel, you should see a list of tickets or issues from the external tool:
   

1. Drag an issue or ticket into the Icebox or Backlog. This will create a new story, linked to the external issue/ticket. Stories that have external links display an “E” in the story icon, as shown here:
   

1. Work on linked stories in Tracker. Depending on the integration type, state changes and comments to linked stories will be reflected in the integrated external tool/application. For example, starting a linked story will mark the corresponding JIRA issue as In Progress, and when the story gets accepted, the ticket will be marked as Resolved.
   

Integrations permissions

This table describes the actions users can take with integrations if they are part of an account with an enterprise plan—whether or not they are a member of an account—as well as the project to which they would like to add an integration, and their role on that project.