Restart a phase in an active release
In an active release, you can abort the current phase and restart the execution from any past phase. This can be required if some parts of the release procedure must be repeated. For example, QA rejects a version of the application for release and the test phase must be repeated with an updated version.
When you restart the release from a previous phase:
- The current phase is interrupted.
- All remaining tasks are skipped.
- The release is paused.
- Release makes a copy of all previous phases that need to be repeated.
The release owner can change variable values and task details before reinitiating the release flow.
Note: If you want to specify the task from which to restart the phase, you must have permission to skip all tasks before the current one. You must have the
edit#task permission on the release, or you or your team own the tasks before the current one. If you do not have permission, you can only restart the phase from the first task.
This is an example of how restarting a phase works in practice. Suppose you have a release with three phases: QA, UAT, and Production.
The QA phase was started with version 1.0 of the product, but bugs were found and QA could not sign off. So the Sign off by QA task failed. The Dev team is notified and produces a fix: version 1.0.1. You can now start the QA phase again for version 1.0.1.
To restart the phase:
- In the top navigation bar, click Restart Phase….
- Select the version of the phase: Latest or Original.
- Select the phase and task from which the release should be restarted.
- Click Continue to confirm the restart. After you continue, the release is paused and the new phases are created.
- To continue the release flow immediately, click Resume now. Note: You can edit variables by clicking Resume later and then selecting Variables from the Show menu.
Release creates a phase called QA (2). You can still modify its content. For example, suppose that the task Update test scenarios is no longer relevant; you can remove it.