Skip to content

feat(group): add escalation hierarchy editor between groups - #28

Merged
MyvTsv merged 5 commits into
escalade-implementationfrom
group_tree_back
Oct 8, 2026
Merged

MyvTsv merged 5 commits into
escalade-implementationfrom
group_tree_back

Conversation

@MyvTsv

@MyvTsv MyvTsv commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor
  • 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

  • It fixes # (issue number, if applicable)
  • Here is a brief description of what this PR does

Escalation between groups had no hierarchy: there was no way to define which groups a group escalates to, per entity.

Screenshots (if appropriate):

image

@MyvTsv MyvTsv self-assigned this Oct 6, 2026
@MyvTsv
MyvTsv added this pull request to stack #29 October 6, 2026 09:54
@Lainow
Lainow force-pushed the escalade-implementation branch from 0a93295 to e7f2471 Compare October 7, 2026 14:23
@MyvTsv
MyvTsv requested a review from Lainow October 7, 2026 14:49
@MyvTsv
MyvTsv marked this pull request as ready for review October 7, 2026 14:49
@MyvTsv
MyvTsv removed this pull request from stack #29 October 8, 2026 12:58
)

* feat(escalation): filter escalation groups with the escalation tree

* Update CHANGELOG.md

* lint
@MyvTsv
MyvTsv merged commit 7c3dd46 into escalade-implementation Oct 8, 2026
7 checks passed
@MyvTsv
MyvTsv deleted the group_tree_back branch October 8, 2026 13:03
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