Skip to content

Feat escalade options - #21

Merged
MyvTsv merged 9 commits into
escalade-implementationfrom
feat-escalade-options
Oct 1, 2026
Merged

MyvTsv merged 9 commits into
escalade-implementationfrom
feat-escalade-options

Conversation

@Lainow

@Lainow Lainow commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

Checklist before requesting a review

Please delete options that are not relevant.

  • I have performed a self-review of my code.
  • I have added tests (when available) that prove my fix is effective or that my feature works.
  • I have updated the CHANGELOG with a short functional description of the fix or new feature.
  • This change requires a documentation update.

Description

Implement the following options in the Escalation tab of the plugin:

  • Remove technicians during an escalation
  • “Ticket” status after an escalation
  • “Change” status after an escalation
  • “Problem” status after an escalation
  • Escalation event is private
  • Assign me as an observer after an escalation by default

Screenshots (if appropriate):

image

@Lainow Lainow self-assigned this Sep 29, 2026
@Lainow
Lainow changed the base branch from main to escalade-implementation September 29, 2026 14:16
@Lainow
Lainow requested a review from MyvTsv September 30, 2026 07:48
@Lainow
Lainow added this pull request to stack #24 September 30, 2026 13:29
@MyvTsv
MyvTsv merged commit 3b24684 into escalade-implementation Oct 1, 2026
7 checks passed
@MyvTsv
MyvTsv deleted the feat-escalade-options branch October 1, 2026 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants