Transitions and attributes

This topic explains transitions and attributes.

Transitions

A transition moves a CR forward or backward in a lifecycle and changes the CR state. For example, the in_review2assigned transition moves the CR from the in_review state to the assigned state.

When you define a transition, identify the attributes you want to include on the Change Request Submission and Transition dialog boxes. Then, establish any security rules based on the transition.

The Transition tab defines both transitions and submissions. A submission is a special transition in which a CR is created in an initial state. When you define a transition, you can define Change Request Submission and Transition dialog boxes. Before doing so, decide which of the available attributes you want to display on the dialog box, and whether the attributes are required, optional (for submission and transition), or read-only (for information purposes only, on transition).

Attributes

Required attributes must be set by the user for the transition to occur. For example, you can require that when a user is completing a resolved2concluded transition, the user must provide conclusion_notes to describe that activity.

Optional attributes can be set by the user, but are not required for the transition to occur. Such attributes might be set already but can be updated by the user. For example, a customer might submit a problem and propose a solution. If the solution is incorrect, the reviewer or assigner can correct it.

Read-only attributes provide information about the CR, such as the CR ID.


Feedback