Change request lifecycle and states

This topic contains examples of possible change request transitions and states based on the dev CR process. If your lifecycle looks different from the lifecycle shown in this topic, it has probably been customized or is a different process.

When you are logged on to the system, a lifecycle is active. For this example, your administrator has installed the dev CR process.

For the User interface, all new change requests begin in the entered or assigned state. The change request then progresses or transitions through each stage in the change request lifecycle, and its state changes.

Ultimately, the change request is either concluded successfully, marked as a duplicate of another change request, made obsolete, or rejected.

This figure shows the possible transitions and states for the dev_process:

Possible transitions and states for the dev process

For more detailed information, see Managing change and releases using Rational Change.

In addition to the dev_process, IBM Rational Change also contains the ecp_process. For additional information about the ecp_process, see Enterprise Change Process: ECP_process.xml.


Feedback