All geek questions in one place

Private registration always associates work items with a string

I use TFS2010 with private logins, and although I set the "Associate Chagesets and Work Items" to false, changes and work items are associated with this assembly.

This only happens on gated lines. If I start the assembly using other registration triggers (manually, continuously, on a schedule), the changes and work items are not associated with the assembly, unless the Related Changes and Work Elements option is set to true.

Any ideas why this is happening? I am using the Visual Studio Scrum process template with default workflow definitions. Maybe the problem is in defining the workflow?

+4
source share
1 answer

Gated-CheckIn strings are by default associated with a set of check-in changes and associated work items. This boolean parameter determines whether non-Gated-CheckIn assemblies should have changes and work items associated with them.

If you look at the default template, you will see that the AssociateChangesetsAndWorkItems action is called when this parameter is set to true, the build reason is not Gated-CheckIn. The display name says this: "Associate with changes and work items for an assembly without a shelf."

I think the description of this parameter is misleading. It says: "Set this to true to associate change commands and work items with the assembly." He should say: "for assembly with a closed record."

+2
source

Source: https://habr.com/ru/post/1392486/

More articles:


All Articles