A lifecycle is a set of rules that governs how users can modify and move change requests to other states within that lifecycle.
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.
Task lifecycle and states
You can create tasks during the assignment transition in a change request lifecycle, or by using IBM® Rational® Synergy. All new tasks begin in either the task_assigned or registered (unassigned) state. The task_assigned state is the default. If the task is associated with a change request, you must transition the task to the completed state before you can resolve the change request.
Customized lifecycles and states
Lifecycles and states can be changed from the delivered processes shipped with the product so that they reflect requirements and processes of your site. The administrator at your site is involved in defining and implementing the required customizations.