What happens to the implementation and testing tasks when a Change request goes to the Review state in the baseline Change - Normal model?

When a Change request transitions to the Review state in the baseline Change - Normal model, the implementation and testing tasks are automatically canceled. This is due to the fact that once the Change request reaches the Review state, it signifies that the Change is being assessed, and any actionable tasks associated with its implementation or testing are no longer relevant or necessary at this point in the process.

This cancellation is a deliberate design in the workflow to prevent any ongoing implementation or testing activities from interfering with the review process, allowing for a clear focus on the evaluation of the Change request itself. By canceling these tasks, the system ensures that there is no confusion and that the Change request can be properly scrutinized without pending activities complicating the assessment.

In contrast, while other options might suggest different forms of task management, they do not align with how the workflow is structured for the Review state. Task closure or assignment would not accurately represent the intent behind the Review state transition, which is to pause any further task progression until a decision is made regarding the Change request.