PivotalTracker
Integrate your Airbrake project with PivotalTracker
Description
With Airbrake’s PivotalTracker integration, you can:
- Automatically create a Pivotal story with error details for every new type of an error
- Manually create a Pivotal story with error details from the Error Dashboard
- Re-open previously accepted, delivered, or finished Pivotal story when a linked resolved Airbrake error re-occurs
- Manually pull Airbrake errors into Pivotal stories from Pivotal
- Automatically create Airbrake comment for every new activity on a linked Pivotal story
Configuration
- Find your Pivotal API token
Your Pivotal API Token is located on your personal profile page. Visit your profile page directly via https://www.pivotaltracker.com/profile or navigate to your profile page by clicking your name in the top right corner and selecting Profile.
- Find your Pivotal Project ID
Retrieve your Pivotal Project ID from the URL of your Pivotal Tracker project’s dashboard or settings page.
- On the PivotalTracker integration page, enter your Pivotal API token (step 1), and your Pivotal Project ID (step 2). Tweak the settings, and click on the Save button
This integration is working both ways, you can manually pull Airbrake errors into stories from PivotalTracker or you can create new Pivotal stories from the Airbrake Error Dashboard.
Settings
| Setting | Description |
|---|---|
| Enabled | Pause/Unpause the integration |
| Auto create Pivotal story when an error occurs | Create a Pivotal story for every new type of Airbrake error |
| Reopen accepted, delivered or finished Pivotal story when a resolved error reoccurs | Reopen linked accepted, delivered or, finished Pivotal story when a resolved error reoccurs |
| Resolve error on Airbrake when Pivotal story is accepted | When a linked story is accepted in Pivotal the Airbrake error is marked as resolved |
| Create Airbrake comment for Pivotal story activity | For every new activity on a linked Pivotal story, create comment on the Airbrake error |
| Only trigger for errors with environments matching “production” (not case sensitive) | Only create Pivotal stories for errors from the “production” environment |