Issue Tracker integrationIssues are now first class citizens in TeamCity. Out of the box TeamCity integrates with Jira, Bugzilla and Jetbrains own tracker Charisma. Plugins can be written to support other trackers. There is also Open API for working with issues. Issue tracker integration is configured on a separate tab of the Server configuration page: After that TeamCity will start recognizing issue ids mentioned in the change or build comments and associate issues with builds. You can see issue details by moving your mouse over issue id:  If build contains changes with issues mentioned in them, then new tab will appear where build related issues are shown:  There is also Issue Log page made similar to Changes Log. It shows issues detected by TeamCity optionally grouped by builds:  TeamCity can also determine in what build an issue is fixed. This works provided all the related checkins have issue id in the comment and developer resolves the issue in the issue tracker. Is this assumption true for your organization? Let us know how do you want to improve the issue tracker integration. Java and .NET CoverageCoverage support was significantly improved in TeamCity 5.0 for both Java and .NET. For Java TeamCity supports new coverage engine: IntelliJ IDEA built-in coverage. Note that there is a known bug in coverage merging: http://jetbrains.net/tracker/issue2/TW-8913 For .NET TeamCity 5.0 supports NCover and PartCover coverage engines and you no longer need to integrate coverage manually. |