User Management in the TFS Assigned Work Item

Question

So, I know that there were several posts in this thread, but I don’t think they got to the end!

So my problem is that when I create a new work item in TFS, the users to whom I can assign it include NT Authority \ Local Service (which is also a TFS service account). I do not ask why, because I know that this field is filled in by the group "Valid Users" by default, and after checking the groups, I see that the hierarchy of group permissions looks like this:

 -> Valid Users
   -> Project Collection Admistrators
      -> Project Collection Service Accounts
         -> NT Authority\Local Service

And you cannot change anything in the accounts of the project collection service, so, by default, everyone has this user in the destination field? Does this mean that everyone agrees with this, or do they modify their process templates to filter it (see the Blog here )?

It seems a little strange to me that the default is no longer filtered! It is clear that I do not want to remove this from any permissions (even if I could), as I am worried that this will cause problems later.

So filtering in a process template is the only way (which looks a bit stressful to maintain), or is there an easier way?

Answer 1

TFS2008 . 2010 "", .

, , , , , " " "" "". , , :

        <FIELD name="Assigned To" refname="System.AssignedTo" type="String" reportable="dimension">
            <ALLOWEDVALUES expanditems="true">
                <LISTITEM value="[Project]\Contributors"/>
                <LISTITEM value="[Project]\Moderators"/>
            </ALLOWEDVALUES>
        </FIELD>