Escalade 2.10.7 does not delete the previous group when assigning a new one

Open
#492 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
php
Domain
backend

Research direction

Start by reproducing the assignment flow in GLPI 11 with Escalade 2.10.7 and the “Remove old group assignment on new assignment” option enabled. Compare the ticket’s assigned groups and escalation history before and after assigning a new technical group; done means the previous group is removed as expected and the relevant escalation event is recorded.

Written by the indexing model from the issue text.

Description

GLPI 11
Escalade 2.10.7

Configuration:

  • Remove old group assignment on new assignment: Enabled

Issue:
When assigning a new technical group to a ticket, the previous assigned group is not removed.

Expected behavior:
The previous group should be automatically removed from the ticket assignment.

Additional information:

  • This worked as expected in previous versions.
  • No escalation history/event seems to be recorded.
  • Ticket ends up assigned to multiple groups.
  • Attached configuration

configuration.docx

Dominant language
PHP
Stars
28
Forks
38
Avg merge
17h 52m
Merged PRs (30d)
13

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pluginsGLPI/escalade

All issues in pluginsGLPI/escalade

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.