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

Ticket gets reopen by an email send via a trigger configured with recipient article_last_sender and article sender was 'customer' #2527

Closed
martini opened this issue Mar 29, 2019 · 3 comments
Assignees

Comments

@martini
Copy link
Collaborator

martini commented Mar 29, 2019

Infos:

  • Used Zammad version: 2.9
  • Installation method (source, package, ..): any
  • Operating system: any
  • Database + version: any
  • Elasticsearch version: any
  • Browser + version: any

Expected behavior:

  • Zammad should not reopen tickets by sending a trigger notification to Zammad it self.

Actual behavior:

  • In certain cases Zammad sends a trigger base email notification to Zammad it self and my reopen the ticket.

Steps to reproduce the behavior:

  • state is changed
  • trigger notification to article_last_sender
  • state is changed
  • trigger notification to article_last_sender
  • close a ticket and you will see 2 trigger based notifications. The second one is sending a email to Zammad it self (because the used article_last_sender is based on first generated trigger based email notification).
@martini martini added this to the 2.9.1 milestone Mar 29, 2019
@martini martini self-assigned this Mar 29, 2019
@martini martini modified the milestones: 2.9.1, 3.1.1 Jul 12, 2019
@thorsteneckel thorsteneckel changed the title Zammad is sending email it self if trigger with recipient is set to article_last_sender and article sender was 'customer'. Ticket gets reopen by Zammad again. Ticket gets reopen by an email send via a trigger configured with recipient article_last_sender and article sender was 'customer' Nov 19, 2019
@thorsteneckel thorsteneckel modified the milestones: 3.1.1, 3.2.1 Dec 9, 2019
@thorsteneckel thorsteneckel modified the milestones: 3.2.1, 3.4.0 Mar 2, 2020
@mantas mantas self-assigned this Apr 28, 2020
@mantas
Copy link
Collaborator

mantas commented May 6, 2020

Likely fixed by #2923 ?

@mantas mantas removed their assignment May 6, 2020
@thorsteneckel
Copy link
Contributor

@rolfschmidt is this a duplicate?

@rolfschmidt
Copy link
Collaborator

yeah i think so. @martini please reopen if you think different but i think it is already fixed with #2923 . Thank you @mantas !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants