This project is read-only.
So you setup TFS Aggregator and it just sits there.... doing nothing...

Well, this is a check list of things to double check.
  • You are using it on a TFS 2010 or TFS 2012 server (and you have the right version for the right server).
  • Any aggregations between work items have a Parent-Child Link.
  • You have updated a work item that needs aggregation. (The TFS Aggregation only works once a work item that has aggregation rules on it is updated. This may change in a future version.)
  • You have updated the AggregatorItems.xml file to use a valid url to your server (an example of a valid url is http://YourTFSServer:8080/tfs/YourCollection)
  • You copied both the DLL and the AggregatorItems.xml file to the plugins location on the TFS Application Tier Server (Usually at: <Drive>:\Program Files\Microsoft Team Foundation Server 11.0\Application Tier\Web Services\bin\Plugins)
  • You have valid names for source and destination fields in AggregatorItems.xml.
  • When you saved the file you saved it as utf-8 encoding (in Notepad ++ it is called “utf-8 without BOM”) (This should not be an issue, but it does not hurt to check).

Also if you are having issues I recommend making a simple AggregatorItems.xml file and trying that out.

Enable Logging

You can also enable Logging if you are using a TFS 2012 Beta or later version. There are two parts to enable logging.

The first is that you have to add a loggingVerbosity attribute to the AggregatorItems element in your AggregatorItems.xml file. There are two valid values, Normal and Diagnostic. Normal will give you just exception messages, Diagnostic will give you detailed logging.

<?xml version="1.0" encoding="utf-8"?>
<AggregatorItems tfsServerUrl="http://[yourTFSServer]:8080/tfs/[yourTeamProjectCollection]" loggingVerbosity="Diagnostic">

Then you need to download DebugView from Microsoft's SysInternals site. DebugView is a Trace Listener and will capture the trace messages from TFSAggregator. You have to run DebugView on the TFS App Tier machine.

I would recommend adding the following filter to DebugView so that you only see the TFSAggregator traces.

Download DebugView at
If you check all the above items and it still does not work then go to and create gists/posts of your simplified AggregatorItems.xml file and the xml of the work item types you are trying to use TFS Aggregator. Send me the links and a description of the problem and I will try to look into why it does not work (the TFS Power Tools allow you to export the xml of work item types, some simple googling can show you how to do this.).

If you do not want to use Gist-GitHub then you can contact me directly at TFSAggregatorIssues<<@>> (remove the <>).

If you have found a bug then I would like to fix it.

Last edited Jun 20, 2013 at 5:33 PM by sstjean, version 11


Mishu007 Mar 5, 2014 at 9:47 AM 
Also when the changes in the AggregatorItems.xml are refreshed?

kwatts696 Dec 30, 2013 at 7:41 PM 
I've added much more logging and helpful, quicly to read and diagnose, information than what your logging has. What about the support for multiple collection support and the bug we found/corrected?

kwatts696 Dec 20, 2013 at 4:48 PM 
We have successfully added logic to support multiple collections, added significant logging that makes debugging a snap, creating a txt log file by collection, plus a bug with aggregating to a parent. Who at CodePlex could I contact?

manishkj Oct 22, 2011 at 1:43 AM 
Suggestion: add verbose log file with switch is xml file.