AssociateChangesetsAndWorkItems activity in Team Build takes only the first 256 Changesets - by SWarnberg

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 778627 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 2/6/2013 12:27:52 AM
Access Restriction Public


The AssociateChangesetsAndWorkItems activity associates only the first 256 changesets between the two build labels. This causes a lot of problems, because the workitems doesn't get correct information in the IntegrationBuild field and those workitems are lost forever.
We also create automated release notes based on this information, so it's quite crucial that the build associates all changesets and not only the first 256.
Sign in to post a comment.
Posted by SWarnberg on 3/4/2013 at 3:12 AM
A month has passed now with no response from Microsoft. Alex2550's answer seems like it could be cause of the problem. However, I'm expecting this to be fixed in a near update or hotfix. This is a showstopper for us, so please provide us some info on this.
Posted by Alex2550 on 2/28/2013 at 10:51 PM
It seems that this issue is caused by behavior of the TFS stored procedure prc_CompareLabels which doesn't support values more than 256 in its' @maxChangeSets parameter.
Posted by Microsoft on 2/6/2013 at 1:25 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/6/2013 at 12:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(