However there must be some somewhere stored the association.
Note 2: We have some special handling in the values, only one of there will contain a value, the other is blank.
Thus allowing the template to work for both GIT and TFVC builds.
Is it possible to update a changeset to include a reference to a work item after the check in has occurred?
For instance you can right click on a changeset, and request a review (rather than requesting a review based on a shelveset before check in).
Update 2013-07-24: This activity is now part of Community TFS Build Extensions.
I’ve said it before and I’ll say it again – TFS is more than just source control. One of the defining capabilities of TFS is integration across the ALM landscape.To reiterate, this doesn't work for me except for the case of attaching a work item like a bug to a changeset after it's been checked in. What I'm saying is that in my system, it appears that this changeset is not linked to the code review that's created.This does not work for creating a link ON a changeset, TO a code review, in the case where a code review was created using Etienne's process above. The code review is linked to the changeset, but not the other way around.Target Environment: TFS 2015 Update 3 We are attempting to get the v Next build system to allow us to to only associate Changesets and Work Items to a build once it is deployed via Release Management.However, the TFS v Next build system automatically associates these items to builds at build time (based on the last successful build).The old XAML build system had a property to turn this off called Skip Get Changesets And Update Work Items, but it no longer exists in the new system.