Team project aggregation

Nov 1, 2011 at 5:00 PM

Very useful tool. Is it possible to aggregate at team project level or is it Collection level only?



Nov 1, 2011 at 5:04 PM

It works off a connection to a TFS Collection.  So currently, it will be collection only. 

So if you have a field with the same name in two different projects, but you only wanted to aggregate one of the projects, you would have to use a Condition on some other field (ie Area Path or Iteration) to make sure you only hit work items in the project you intend to aggregate on.

Nov 1, 2011 at 6:27 PM

Thanks for the very prompt response! Team projects can change Area Path so I guess this field could only be used if a StartsWith operator was available, however there is a very useful 'Team Project' field on each TFS work Item so problem solved! 

Just a further question regarding behaviour and performance

Does a work item change event trigger the aggregator code and does the aggregator only check any linked work items as per the XML configuration parameters i.e it doesn't trawl through all work items in the collection applying the checks? So if we implemented team project level aggregation,whilst the aggregator code would be triggered for all work item changes, no changes would be made to non-matching team project work items.


Nov 1, 2011 at 9:37 PM

It only checks work items that are changed (or are related as per the configuration to the changed work item).

Nov 3, 2011 at 4:04 PM

Thanks for your help