mirror of
https://github.com/Unleash/unleash.git
synced 2025-02-04 00:18:01 +01:00
docs: add a note about suspended change request schedules (#5874)
This PR describes in closer detail what happens when the user who scheduled a change request is deleted. It mentions the new suspended state and what the user can do to get out of it.
This commit is contained in:
parent
39145e2617
commit
b1d7c27124
@ -91,7 +91,7 @@ When a scheduled change request is applied, the person who scheduled it and the
|
|||||||
|
|
||||||
#### Edge cases: what happens when ...?
|
#### Edge cases: what happens when ...?
|
||||||
|
|
||||||
If the user who scheduled a change request is deleted from the Unleash users list before the scheduled time, the changes will **not** be applied.
|
If the user who scheduled a change request is deleted from the Unleash users list before the scheduled time, the changes will **not** be applied. Instead, the schedule will be put into a special **suspended state**. A change request with suspended schedule will not be applied at its scheduled time. A user with the required permission can reschedule, apply, or reject the change request. Any of these actions will put the change request back into the regular flow.
|
||||||
|
|
||||||
If a change request has been scheduled and change requests are then disabled for the project and environment, the change request **will still be applied** according to schedule. To prevent this, you can reject the scheduled change request.
|
If a change request has been scheduled and change requests are then disabled for the project and environment, the change request **will still be applied** according to schedule. To prevent this, you can reject the scheduled change request.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user