When you commit files to your source code repository, use the commit comment to
quickly link your commit with one or more tracker artifacts or other
TeamForge items.
Associations track the links between code and the bugs, feature requests, or other
tracker artifacts that the code addresses. You can also associate code commits with
other
TeamForge items, such as tasks or
documents.
A project administrator can make associations mandatory for all code
commits. When this is made mandatory, the following additional rules pertaining to
code commit can also be set:
- Code commits can be performed only for open artifacts.
- To perform a code commit, the committer must be the owner of the specific
artifact.
Note: Once you enforce the above rules, validations are strictly enforced for
commits against tracker artifacts only. In case you commit against any other
TeamForge object, for example a wiki or a document, mere existence of the object
ID ensures successful commit and association and no validations are performed
against the status of the object or who it is assigned to.
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 TeamForge.
Use the same syntax for commits to CVS and Subversion
repositories.
When making a code commit, add the associate command in the commit message like
this:
[<item id>], such as the
TeamForge tracker 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 TeamForge items, separate the item
IDs with commas.
- All associations are displayed in the
ASSOCIATIONS tab of the Commit
Details page.
- The Comment section lists the comments made with
each commit.
Note: To associate an object in an integrated application, use the
[<prefix_objectid>] format. Each integrated
application displays its prefix on moving the mouse over the application
name.
Note: When you commit files to your source code repository,
a source code commit notification mail is sent to users who are monitoring that
source code repository.
An option is provided at site level and user level to
make sure whether the notification mail has to be sent or not. For more
information on this, see Configure your site's settings.