Skip to main content
Solved

Stop email notifications for some status changes

  • August 27, 2024
  • 5 replies
  • 123 views

Forum|alt.badge.img+1

I have my settings configured to send me a notification email when my tickets are updated (“when your ticket status, assignment, or asset changes”) which is okay...most of the time. This triggers two emails when a ticket is created via someone sending an email to the system. I get notified that a new ticket has been created but I also get an email because the status has changed from ‘From Email - Validating' to 'Submitted'. Can I set up a rule that stops the system from sending the status change email for just this scenerio?

Best answer by Kathryn Carter

@KBremner 76000e4 mtbluersd This looks like it might be an issue on the backend, then. Please submit a ticket to support to get this escalated. 

 

5 replies

Kathryn Carter
Forum|alt.badge.img+18
  • Community Manager
  • August 27, 2024

@KBremner 76000e4 mtbluersd Thank you for submitting your question to our community! 😄

Are you automatically added to those tickets? If so, we can adjust your settings based on whether you are a follower or an agent so it only adds you to those emails once they are assigned to you. 


Forum|alt.badge.img+1

These would be tickets that I am assigned as the agent or as a follower by a rule.


Kathryn Carter
Forum|alt.badge.img+18
  • Community Manager
  • August 29, 2024

@KBremner 76000e4 mtbluersd So I took a look at your rules and you have overdone yourself. I would suggest creating ONE created from email rule that approves the ticket creation, then within “when created” and add all your assignments there. If you have a specific user who needs to work tickets from email, you can add that as a filter. 

Does that make sense? 


Forum|alt.badge.img+1

I cleaned up my ‘when from email’ rules like you suggested but I still have the issue of the double email.

 


Kathryn Carter
Forum|alt.badge.img+18
  • Community Manager
  • Answer
  • September 10, 2024

@KBremner 76000e4 mtbluersd This looks like it might be an issue on the backend, then. Please submit a ticket to support to get this escalated.