Team Development with Visual Studio Team Foundation Server

This creates a transition that has no source. There should only be one such
transition on the diagram; if one already exists, you need to delete it.
e. To see a summary of the attributes of each state or transition, click the
expand/collapse icon at the top right of the shape. In the list of fields in the
summary, “+” marks a field that has a required rule; “-” marks a field that has
an empty rule; and “*” marks a field that has other rules.
f. To edit the attributes of each state or transition, right-click the state heading,
and then click Open Details or double-click the heading.
Note: If the WITDesigner toolbox is not visible, click Toolbox on the Visual
Studio View menu.
2. Edit the rules governing a state as follows:
a. Right-click the state heading and then click Open Details, or double-click the
heading.
This opens the Workflow State Field Rules dialog box. Each item in the list
refers to a field of the work item type, and represents a set of rules governing
that field while the work item is in this state.
b. On the Field Reference tab, set the RefName to indicate the field you want to
constrain while the work item is in this state. The drop-down list of available
fields that you can set is located on the Fields tab of the work item type.
c. On the Rules tab, click New to create a new rule, or click Open to edit an
existing rule.
The details provided in the dialog box on opening a rule vary depending on
the type of rule.
d. Click OK to complete your changes.
3. Edit a transition as follows:
a. Right-click the transition heading and then click Open Details to open the
Workflow Transition dialog box.
• The Transaction Detail tab defines the From and To states of the
transition. If this transition marks the initial state in which a new work
item of this type is created, the From state is empty. These fields
correspond to the links on the workflow diagram. The For and Not fields
can contain the name of a user or group who can or cannot make the
transition.
• The Reasons tab defines the content allowed in the Reason field when the
transition occurs. There should be at least one reason for every transition.
• The Actions tab defines the state transition actions necessary to automate
transitions of work items at various points in their workflow. For example,
a TFS version control system needs to support automatic transitions of
work items at check-in time.
• The Fields tab defines rules constraining fields when the transition occurs.
b. Click OK to complete your changes.