Administration > Server Configuration > Issue Tracker tab
The Issue Tracker tab allows to create and configure connection to an issue tracker. When a connection is created and configured, TeamCity will search all commentaries made by a committer to a build or a change, and if it founds a certain pattern (for example, TW-1423) it transforms such pattern into link to the issue at the issue tracker.
All existing connections to issue trackers are shown in the Issue tracker connections list.
| Item |
Description |
| Create new connection |
Click to open the Create New Connection dialog and configure new connection to an issue tracker. |
| edit |
Click to edit settings of the connection. |
| delete |
Click to delete the connection to an issue tracker. |
Create / Edit Issue Tracker Connection Dialog
| Option |
Description |
| 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 |
Username to log in to the issue tracker, if it requires authorizing. |
| Password |
Password to log in to the issue tracker, if it requires authorizing. |
| Additional Fields |
These depend on the issue tracker type that is being configured. The fields configure what strings are recognized by TeamCity as links to issue IDs.
Project Ids (YouTrack): Space-separated list of YouTrack project ids.
Project Keys (Jira): Space-separated list of Jira project keys. Also use Get all projects link to fetch all projects from the issue tracker and fill Product Keys field automatically.
Issue Id Pattern (BugZilla): A Java Regular Expression pattern to find issue ID in the text. The matched text (or the first group if there are groups defined) is used as issue number. Most common case seems to be #(\d+) - this will extract 1234 as issue ID from text "Fix for #1234". |
Test Connection
You can test whether you have configured the connection correctly using Test connection button. It opens another Test connection dialog where you need to enter arbitrary issue id and then click Test to check connection settings.
The result of the test connection, whether successful or not, will be displayed right in the dialog:
See Also:
