Tracking Source Code Changes and Developer Team Activity through Commit Notification Emails

Codebeamer»Wiki»User's Guide»codebeamer ALM: Application Lifecycle Management»Version Control: Subversion (SVN), Git, Mercurial

Tracking Source Code Changes and Developer Team Activity through Commit Notification Emails #9379/HEAD / v152

[WIKIPAGE-9379] Tracking Source Code Changes and Developer Team Activity through Commit Notification Emails

Tags: Commit Notification

Tracking Source Code Changes and Developer Team Activity through Commit Notification Emails

One of the hardest to manage tasks for a development project supervisor is tracking the state of the source code. CodeBeamer makes it amazingly easy even if the team is large, by sending notification emails after each commit.

These emails contain detailed information about:

the project that the change was committed to
tracker items related to the change (e.g. a task accomplished or a defect fixed)
list of added, deleted or modified files
highlighted unified format differences

Here is a sample email:

[!Screen Shot 2013-02-04 at 10.39.01 AM.png!] :