Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

The escalade task doesn't appear in sent notifications

Open
#503 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the issue using the listed escalation and notification steps, then trace the notification generation for the "New group in assignees" event and its timeline-item list. Done means the notification for an escalation includes the latest escalation rather than showing it only in the next notification.

Written by the indexing model from the issue text.

Description

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

11.0.9

Plugin version

2.10.8

Bug description

Notifications for "new group in charge" are triggered on ticket escalation but do not display the escalation in the list of timeline items.

However, it appears in subsequent notifications. I suppose the notification text is computed before the escalation is actually added to the ticket.

Relevant log output

Page URL

No response

Steps To reproduce
  1. Escalation tasks are public
  2. Configure a notification with standard "Tickets" template (are any other template including the list of timeline items) to be sent on the "New group in assignees" event
  3. Escalate a ticket and check the notifications : the escalation does not appear
  4. Escalate once again : the previous escalation appears, but not the latest
Your GLPI setup information

No response

Anything else?

No response

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.