Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dual notification on escalade #213

Open
hcimadomo-procsi opened this issue Jul 11, 2024 · 16 comments
Open

dual notification on escalade #213

hcimadomo-procsi opened this issue Jul 11, 2024 · 16 comments

Comments

@hcimadomo-procsi
Copy link

Hello,
glpi 10.0.15/escalade 2.9.7:
An escalation to a new group generate dual notification : one for the old group and on for the new group. The configuration for notification is "new group in assignees" and " groupe chargé du ticket" in destinataire.
any idea ?
BR

@Windayz
Copy link

Windayz commented Jul 13, 2024

Well, if you've set up the old and new groups to receive a notification, it's normal for them to do so, isn't it?

@DEF-IT
Copy link

DEF-IT commented Jul 15, 2024

Hello, since the update to GLPI 10.0.16 and escalade 2.9.7 we are facing nearly the same issue.
When a ticket is escalated to a new group, the system send the email twice to the new group.
In notification only "groupe chargé du ticket" is set for "New group in assignees"
It was working well prior to the update.
Thanks for your help

@Gaelolito
Copy link

Hello,
Same case with GLPI 10.0.16 / Escalade 2.9.7
When a ticket is escalated to a new group, the system send the email twice to the new group.
Parameter notification :
2024-08-26 09_53_27-Notification - TIBCO_TKT_Nouveau Groupe Technicien - GLPI
Thanks for your help

@hcimadomo-procsi
Copy link
Author

Well, if you've set up the old and new groups to receive a notification, it's normal for them to do so, isn't it?

No, the target of notification "new group in assigned" is "last group assigned". Same with "group assigned"
This work well with escalade version 2.9.4.

@hcimadomo-procsi
Copy link
Author

same issue with 2.9.8.
BR

@stonebuzz
Copy link
Contributor

Hi @hcimadomo-procsi , @DEF-IT , @Gaelolito , @Windayz

can you retry by using "main" branch ?

@Windayz
Copy link

Windayz commented Sep 4, 2024

Hi @hcimadomo-procsi , @DEF-IT , @Gaelolito , @Windayz

can you retry by using "main" branch ?

everything is working properly, I haven't detected any bugs yet.
except for one small detail: if a mandatory field hasn't been filled in and you change the technician group and validate, it gives you an error because you haven't filled in the mandatory field, but the plugin still displays the “escalate to...” bubble.
Otherwise, all's well.

@stonebuzz
Copy link
Contributor

@Windayz

can you open new issue for this ?

@Gaelolito
Copy link

Hi @hcimadomo-procsi , @DEF-IT , @Gaelolito , @Windayz

can you retry by using "main" branch ?

Escalade 2.9.8
Destinataire : New group assignee
always 2 identical notifications sent to each technician in the group
2024-09-04 11_33_28-File d'attente des notifications - GLPI

@Windayz
Copy link

Windayz commented Sep 4, 2024

always 2 identical notifications sent to each technician in the group

yes, I'm wide awake but he's right, there are two notifications sent.

@DEF-IT
Copy link

DEF-IT commented Sep 23, 2024

Hello, using version 2.9.9 still have double notification.

@Gaelolito
Copy link

Hello,
I have always double notification with 2.9.9

@DEF-IT
Copy link

DEF-IT commented Oct 10, 2024

Hello, it seems that commenting the line 413 of the ticket.class.php fix the problem. I receive one notification (the one with previous + new group).
In fact the double notification problem was

  • one notification with only the new group being escalated to
  • one notification with the old group and the new group

@stonebuzz
Copy link
Contributor

@DEF-IT no impact on other notifiactions?

@Gaelolito @Windayz @hcimadomo-procsi con you confirm ?

@DEF-IT
Copy link

DEF-IT commented Oct 11, 2024

@DEF-IT no impact on other notifiactions?

@Gaelolito @Windayz @hcimadomo-procsi con you confirm ?

Well, it seems to work fine, despite the notification should only be the one for the escalated group not the one with both old group + new group. Old group are being notified while they don't need too.

This modification was provided by someone of infotel while troubleshooting another issue.

@Gaelolito
Copy link

I can't test until Monday
I'll keep you posted

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

No branches or pull requests

5 participants