Defects Management using Pivotal Tracker

Report test case failures as bugs in Pivotal Tracker

Vishal Vaswani avatar
Written by Vishal Vaswani
Updated over a week ago

Integration with Pivotal Tracker as a defects manager is the next in the series of defects managers that TestCollab supports.

With the configuration done, the issues can automatically be reported on Pivotal Tracker, in the event of a test case failure of the test opts so while running it.

The defects settings can only be done by administrator(s) of the company. To configure, use "Defects" option under "Settings" menu.

Configuring Pivotal Tracker as defects manager


  • The process starts by enabling defects management for the current project

  • Selection of Pivotal Tracker as defects / issue manager

  • Provide the API token for Pivotal Tracker to connect your account

  • Select Pivotal Tracker project followed by Story type and value for other properties

  • You can also opt to show certain Pivotal Tracker fields on report defect page

  • Save the settings

  • Optionally you can test the settings to make sure that a test issue is reported in Pivotal Tracker

Connecting other user's Pivotal Tracker accounts

Let us now see how a user, other than the administrator (who has configured defects management) can link his/her Pivotal Tracker account to be identified as an issue reporter.

After navigating to defects management settings page, user can provide his Pivotal Tracker API token to connect his account.

Once user has linked Pivotal Tracker account, he would be treated as reporter for the issues reported by him while running test cases.

Reporting defect

To know how tester can report defect at the time of running a test case if it fails, please refer this article.


  • Integration with Pivotal Tracker is available for companies on Premium or higher plans.

  • If you encounter an error that is not specific to the defect being reported then please consider checking the project specific defects management settings to see if the connection you configured is still valid, as sometimes change in Pivotal Tracker profile / API token may invalidate the connection.

Did this answer your question?