Summary

Currently, in the Release Orchestration (Release Management) module, there is no native option to re-run an existing release. If a release needs to be executed again (e.g., due to a transient failure or a requirement to repeat a specific release cycle), users must manually create an entirely new release.

Problem

For customers with complex release structure, creating a new release from scratch for every re-execution is a redundant manual effort that introduces operational overhead and slows down the delivery lifecycle.

Proposed Enhancement

Add a "Re-run" or "Restart" action for a Release. This should allow users to:

Trigger the full release orchestration again using the existing configuration.

Ideally, choose between re-running the full release or resuming/re-running from a specific failed stage.

Maintain a link or history between the original release attempt and the re-run for auditability.

Impact

This will significantly improve the developer experience by reducing the manual steps required to handle release repetitions or failures, ensuring a more streamlined and efficient Release Orchestration workflow.