Transitions Overview

Transitions move primary items from state to state. Most transitions are available as buttons on state forms. Users click a transition button to initiate the transition. In many cases, users can enter data about an item on a transition form before completing the transition.

Transitions can be customized in many ways. For example, you can:

Specify that a transition applies only to certain item types, such as bugs and problem reports. See Restrict By Type Tab of the Transition Property Editor.
Specify that only members associated with particular roles can use the transition. See Restrict By Role Tab of the Transition Property Editor.
Create a rule to determine when a transition is available. See Restrict By Rule Tab of the Transition Property Editor.
Add custom transition controls (buttons, hyperlinks or images) to a custom state form. These controls can be used in addition to or instead of the standard buttons. See Behavior Tab of the Control Property Editor.

Inheritance Rules for Transitions

Every transition contains a set of properties that define how the transition acts, such the originating and receiving states, and the fields needed for data collection from users during the transition. These types of transition properties are inherited throughout the application workflow hierarchy. This lets you configure transition properties once rather than for each workflow.

For example, in an application workflow, you can create transitions that are needed throughout all the workflows. The individual transition properties, like the From and To properties, are set once in the parent workflow and inherited in any sub-workflows and duplicated workflows.

Transitions Overview

Inheritance Rules for Transitions

Related Topics