Save the state of manually skipped steps


We have a big project, that consists of 30 steps. I would like to have an opportunity to deploy different set of steps per release to multiple environments.
Is there a way to save manually skipped steps when promoting to another environment?
For example, to have them in the same state as in previous environment, but allowed to be changed.


Thanks for reaching out!

If you are consistently going to skip certain steps on certain environments on each release, then you should really be scoping those steps the environments where they will be consistently running.

Now, if this is something that you’ll plan on changing on demand for each release (not a repeatable process), then I’m afraid you’re gonna have to do it manually each time, as there’s now way to save manually skipped steps between promotions.



This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.