Repository navigation
feat(escalation): add "remove old assign group" checkbox to escalation form - #509
Draft
UncleTomsCabi wants to merge 3 commits into
Draft
UncleTomsCabi wants to merge 3 commits into
UncleTomsCabi wants to merge 3 commits into
Conversation
stonebuzz
marked this pull request as draft
October 2, 2026 07:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a "Remove old assign group on new group assign" checkbox to the timeline escalation form, so the technician can decide on each escalation whether previously assigned groups are kept or removed.
Context
The two behaviours conflict when they are controlled by one global switch. This PR keeps the #496 behaviour unchanged and adds a per-escalation choice to the Escalade form only.