TeamCity supports Jira, Bugzilla and YouTrack issue trackers out of the box. Refer to the Supported Platforms and Environments page for the list of supported versions. When integration is configured, TeamCity automatically transforms an issue ID (=issue key in JIRA) mentioned in VCS comment into a link to the corresponding issue and allows to see basic issue details on hover over an icon displayed near the issue ID.
Issues fixed in the build can also be viewed on the Working with Build Results tab of the build results.
On the build configuration home page, you can review all the issues mapped to the comments at the Issue Log tab. You can filter the list to particular range of builds and view which issues where mentioned in comments, and their state.
Recommendations on Using Issue Tracker Integration
To get best results out of issue tracker integration we recommend to:
When committing changes to your version control always mention issue id (issue key) related to the fix in the comment to commit.
Resolve issues when they are fixed (time of resolve does not really matter).
Use Issue Log of a build configuration to get issues related to builds; turn "Show only resolved issues" option on to show only issues fixed in the builds.
Enabling Issue Tracker Integration
To enable integration, you need to create connection to your issue tracker on the Administration | Issue Tracker page.
The described below settings are common for all issue trackers:
Connection type
Select type of your issue tracker from the list.
Display name
Symbolic name that will be displayed in TeamCity UI for the issue tracker.
Server URL
Issue tracker URL
Username/Password
Username/password to log in to the issue tracker, if it requires authorizing.
In addition to these general settings you also need to specify which strings should be recognized by TeamCity and converted to links to issues in your issue tracker. For details, please refer to corresponding section:
Requirements: Information about the issues is retrieved by the TeamCity server using the credentials provided and then is displayed to TeamCity users. This has several implications:
TeamCity server should have direct access to the issue tracker. (Also, TeamCity does not yet support proxy for connections to issue trackers).
The user configured in the connection to the issue tracker should have enough permissions to view the issues that can be mentioned in TeamCity. Also, TeamCity users will be able to view the issue details in TeamCity for all the issues that the configured user has access to.
Integrating TeamCity with Other Issue Trackers
To integrate TeamCity with an issue tracker other than Jira/YouTrack/Bugzilla, you can configure TeamCity to turn any issue tracker issue ID references in change comments into links. See Mapping External Links in Comments for details.
