Associate a tracker artifact with a code commit

When checking in files to your SCM repository, you can create links to one or more tracker artifacts or other CollabNet TeamForge items.

Associations track the relationship between code and the bugs, feature requests, or other tracker artifacts that the code addresses. You can also associate code commits with other CollabNet TeamForge items, such as tasks or documents.

A project administrator can make associations mandatory for all code commits.

You can create tracker artifact associations from whatever interface you normally use to check code into your SCM repository. You do not have to log into CollabNet TeamForge.

Use the same syntax for commits to CVS, Subversion, and Perforce repositories.

When making a code commit, add the associate command in the commit message like this: [<item id>], such as the TeamForgetracker artifact ID or task ID.

TeamForge item IDs are always letters followed by four or more numbers, such as task1029 or artf10011.
To associate a commit with multiple CollabNet TeamForge items, separate the item IDs with commas.
All associations are displayed in the Associations section of the Commit Details page.
The Comment section lists the comments made with each commit.

Tip: To remind yourself of the details of the association later, look in the Change Log tab of the associated Artifact Details page.