Notification bug on escalation

未關閉
#53 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
56/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
php
領域
backend

研究方向

Start by tracing the escalation steps in the plugin and how they update the ticket’s assigned group and trigger the “new group in assignees” notification. Compare that flow with the manual group change behavior referenced in GLPI PR 15623. The reproduction steps provide a way to verify completion: after escalating from Tech group 1 to Tech group 2, only members of the new group should receive the notification.

由索引模型根據 Issue 內容生成。

描述

Code of Conduct
  • I agree to follow this project's Code of Conduct
Is there an existing issue for this?
  • I have searched the existing issues
GLPI Version

12.0.2

Plugin version

1.0.1

Bug description

Hello,

On ticket escalation, notifications to "Group in charge" are sent to members of both the old and new assigned group.

I believe it was a core GLPI issue that has been fixed recently (by this PR? https://github.com/glpi-project/glpi/pull/15623) if the group change is done manually, but the issue persists with the escalation.

Is it planned to change this behavior ? Thank you

Relevant log output

Page URL

No response

Steps To reproduce
  • start from a fresh install
  • create "Tech group 1" and "Tech group 2", populate them with technician users
  • enable "new group in assignees" notification
  • create a ticket, assigned to "Tech group 1"
  • escalate the ticket to "Tech group 2"
  • an email is sent to the members of both groups
Your GLPI setup information

No response

Anything else?

No response

主要語言
PHP
星號
3
分支
4
平均合併
16 小時 39 分鐘
30 天內合併 PR
18

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

相似的 Issue

更多 PHP Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。