Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6630335
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T22:23:18+00:00 2026-05-25T22:23:18+00:00

I have work item type template where i want to assign right to change

  • 0

I have work item type template where i want to assign right to change drop down list to
default value as “Requested” for new item and every one can see and read it.
If user is in group “[TEAM FOUNDATION]\Approvers” or “[TEAM FOUNDATION]\Developers” they are able to change this item.

I have a problem if user is not in either of the groups it will fail and blank display disabled field.
How do i define these permissions?

My definition of field is below.

<FIELD name="Approval" refname="Approval" type="String" reportable="dimension">
    <REQUIRED />
    <DEFAULT from="value" value="Requested" />
    <ALLOWEDVALUES>
      <LISTITEM value="Approved" />
      <LISTITEM value="Requested" />
      <LISTITEM value="Rejected" />
    </ALLOWEDVALUES>        
    <DEFAULT from="value" value="Requested" />
    <READONLY not="[TEAM FOUNDATION]\Approvers" />
    <READONLY not="[TEAM FOUNDATION]\Developers" />
    <HELPTEXT>Shows whether the task has been approved by management.</HELPTEXT>
  </FIELD>
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T22:23:19+00:00Added an answer on May 25, 2026 at 10:23 pm

    This seems like a heavy one.What is your exact intend?
    Maybe using a WHEN block or splitting the restrictions into basic ones (at the field definition) and special ones at state or transition level will solve your problem?

    <FIELD name="Approval" refname="Approval" type="String" reportable="dimension">
        <REQUIRED />
        <DEFAULT from="value" value="Requested" />
        <WHENNOT field="System.State" value="New">
          <READONLY not="[TEAM FOUNDATION]\Developers"/>
          <READONLY not="[TEAM FOUNDATION]\Approvers"/>
        </WHENNOT>
        <HELPTEXT>Shows whether the task has been approved by management.</HELPTEXT>
    </FIELD>
    

    or

    <FIELD name="Approval" refname="Approval" type="String" reportable="dimension">
        <REQUIRED />
        <ALLOWEDVALUES>
          <LISTITEM value="Approved" />
          <LISTITEM value="Requested" />
          <LISTITEM value="Rejected" />
        </ALLOWEDVALUES>        
        <DEFAULT from="value" value="Requested" />
        <HELPTEXT>Shows whether the task has been approved by management.</HELPTEXT>
    </FIELD>
    
    <TRANSITION from="" to="New">
        <FIELDS>
            <FIELD refname="Approval">
                <READONLY not="[TEAM FOUNDATION]\Developers"/>
                <READONLY not="[TEAM FOUNDATION]\Approvers"/>
            </FIELD>
    </TRANSITION>
    

    By the way: You should refName your fields with a whole “Namespace”, e.g. “My.Company.TfsFields.Common.Approval” or “My.Company.TfsFields.Bugs.IsRegression”

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a TFS 2010 Work Item Type with a custom field called Requested
I have to work with an existing DB and right now I have to
When I import a Work Item Type from Team Review , I get this
I have the following xaml; <DataTemplate DataType={x:Type NameSpace:Node}> <StackPanel Orientation=Horizontal> <TextBlock Text={Binding Item.Value}/> <ContentControl
I have some problems with making Javascript work with Django template inheritance. According to
I am attempting to add a Requested By field to a custom Work Item
Say I have two classes created work and workItem. CWorker *work = new CWorker();
The commandlink link2 does not have work after an ajax call is made to
I have inherited work from a previous employee. The issue I'm having is a
I have to work on a database in which there are many stored-procedures &

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.