I set up an automation to change resolved tickets to closed. The automation works fine, but I receive e-mail notifications every time the automation completes.
If I manually close a ticket, I do not receive the notification. The automation is what is sending the e-mail.
How can I turn off these notifications?
I tried the instructions in the following link, but it is 3 years old and I am not seeing the checkbox for This rule should send emails.
In addition to what @Michael Andolfatto has mentioned, it is my understanding of Automation for Jira - only EDIT Issue action give you the ability with the checkbox on "send notification".
Another thing that you should check with Automation for Jira rule is who you selected as the rule actor. As stated in this link - https://support.atlassian.com/cloud-automation/docs/run-jira-rules-as-another-user/,
Notifications: The person you select as the new rule actor will receive an email notification to inform them of this change. They’ll also receive emails for each action that is performed on their behalf.
If you set the actor instead of "Automation for Jira" user to "User who triggered the event", then it should eliminate the notification when rules are being executed. You should also adjust your project's notification scheme when needed to remove unwanted notifications as needed by adjusting the recipient(s) of each issue events. Lastly by default, system notifications are set to 1) All watchers (this is the same as JSM requested participants of an issue), 2) Current Assignee, and 3) Reporter.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Viasat Inc.
Hey @Eric H15 , is the notification you receive the standard Jira notification for "someone transition this issue from X to Y?"
It may be because you have your preferences set to not notify you for your own changes (which is why you don't get them when manually closing an issue) but the actor for this rule is technically a different user which is why they go through.
This should be able to be fixed by changing the rule actor to be the user that triggered the event (rather than the default Automation for Jira actor)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Michael Andolfatto ,
Thanks for the response. This appears to work if the automation is triggered from a user-action, but in my case the trigger is an SLA breach (I'm trying to auto-close tickets after they are resolved for a few days).
Is there no other direct way to disable these notifications?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Eric H15 - Your project's notification scheme will send out emails based on certain actions (issue's edited, transitioned, created, etc.) You can remove recipients from this scheme if you would really like to disable emails from this action (please note this will affect other users of the project as well)
Otherwise, you may want to introduce a filter to your inbox. I have a few custom ones set up to ignore/delete emails with specific wording.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Michael Andolfatto I believe I updated my notification scheme and removed notifications for when tickets are closed. This did not work.
Introducing a filter to my inbox is not good. What are other people doing? Just manually closing tickets?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please take a look at my response in your ask. Let me know if it helps you.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.