I came here with darkness in my heart because this annoying issue is still unresolved. Please, fix this simple thing. Your actions will improve life every so slightly for many thousands of people each day. IT IS A NO BRAINER

Every automation we create should have a checkmark to activate or turn off the notifications for that automation specifically. Some automations need a notification, some don't.

Let it on by default, that's fine, but allow admins to turn it off on a case by case basis.

I work at a company with thousands of team members using Jira everyday. For a few years now, since we have begun using Automation for Jira, every morning there is "9+" on my notification bell in Jira/Confluence and it's just issue after issue after issue... "updated by Jira for Automation". It make the notifications feature, which is typically very useful, quite invaluable. 89403358cf11 the sooner a resolution can be made available to resolve this, the sooner we will gain a high value feature back that has been lost for us for years. Thank you.

And for the love of all that is unholy as well... Please get rid of these unnecessary notifications.

Please, for the love of all that is holy, fix these unnecessary notifications. 

This is my #1 request: In giant environments, my important notifications are lost away by automation spam. 

As an alternative, perhaps a 2nd bell for automation notifications? People want notifications on human updates. 89403358cf11 I believe this can now be promoted from "gathering interest" to the next stage at this point.

How on Earth is this still not implemented. We were considering moving away from Jira anyway and the constant notification spam (rendering the notification system essentially useless) is not helping your case.

Incredible that this is still an issue

89403358cf11 skahol This has the MOST votes (836) on the entire AUTO board and still hasn't been moved out of "Gathering Interest". I think it's abundantly clear that the interest is there. What's the hold up?

Its a real shame that even you guys, the maintainers, aren't able to demonstrate JIRA being effective for change management.

Any news on this? Was considering Jira, but the notifications is an issue that will not be OK with the users.

Agree with everyone, we have so many automations set up that we get 4-5 notifications per HOUR for each issue, therefore can't really make use of the notifications anymore and are working with automation emails etc. as a workaround - insanity, to leave Jira and its built in functionality for notifications, simply because we cannot control Jira automation related notifications.

This feature is highly anticipated on our end.
Especially since we're using the JSM Workaround for Email-Signatures. We'd get 3-6 notifications for each Ticket created depending on the Number of Images in the Signature.

This jitter makes it near impossible to be on alert for more interesting Actions caused by automation, like a Ticket being reopened.

We are waiting for this feature

+1 Any Update on this?

Automation notifications create such an overload of updates that the useful ones are swamped and incentivize the team to ignore all of them. We need a way to disable these at the project level.

+1

We use automation to do calculations on fields.  For example, we have a fields called "Escrow Amount Required", "Escrow Amount Used" and "Escrow Balance".  Whenever we get a bill that requires escrow payment, I enter the new amount in "Escrow Amount Used" and automation calculates the "Escrow Balance". I don't need a notification, nor does anyone watching the issue on this.  It would be great to have a simple check box "suppress notification" or something like that on the rule, to prevent mailbox clutter.

As our use of Jira grows, and our use of automation grows, this is more and more becoming an absolute requirement.

We use automation to assign requests to their appropriate teams. The reporter doesn't need a notification stating that the field has been updated, or that their hardware assets has been added to the ticket.
We also have post-creation automation that sends updates to assignees or other stakeholders that we would really rather be without.

+1.

Need better control over which automation actions should / are allowed to trigger email and in-app notifications. Only if configured to allow should other notification settings (e.g. personal, reporter, watcher, etc.) be evaluated to determine if notifications should be sent for the automation actions.

I want to be able to have more control over the email notifications. If an automation rule executes, to create a new story, I want to be able to specifically put a rule in that automation to NOT send the email. I don't want to turn the emails off for ALL newly created stories, just for certain ones that are created from certain rules.

I also want the flexibility to have emails sent to be when Bugs, Stories, Tasks are created, but not then sub-tasks, test plans, and test executions are created.

I'm an Atlassian administrator and have many automations for our Jira Service Management set up. Especially the "Do it once a day for all issues applying to filter xyz"-Automations completelly clog my notifications and the one of my team mates on monday morning. I can't use my own user for those automations because when I did that my team mates were texting me being confused what kind of changes I'd do on their issues when it was just an automation. Please let me mute this Automation for Jira user specifically

+1

+1

+1

+1

+1

+1

+1

+1

This is the most voted feature upgrade. Could you please check here?

Below Teams dropdown my top collaborators are "Jira Misc Workflow Extensions", "Automation for Jira" and "Script Runner for Jira".  Completely nonsense as well. This request relates to all add on users and the concept of how these are supposed to be used in the cloud. Please rethink how you handle this on a bigger scale. E.g. I do not want a notification if a issue is automatically assigned to me after I start working on it. On prem this actions ran as current user and therefor did not send notifications...

Every time our organisation needs a basic, trivial feature added to a project, I’m led to yet another ancient, ignored feature request. This has become a daily joke. I’m constantly disappointing and failing our team because of this inferior product that seems stuck in alpha. What on earth are you doing with your time?

Has there been any traction on this? It's causing alert/notification fatigue to receive so many email AND Jira notifications. We should be able to customize each of them.

+1

this is causing lot of unwanted additional work for the team..needs to be addressed ASAP

This is important for many people, please implement.

+1

+1

+1 !

+1

+1!!

+1 ...

+1 - I don't need our engineers spammed with rules I've added for adminstrative/management reasons - enable this asap, please!

Need this yesterday !! +1 

706b6229d003 There's only one known workaround, but it doesn't work for all use-cases: https://jira.atlassian.com/browse/AUTO-602?focusedId=3021112&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3021112

TL;DR: set the trigger's actor to 'User who triggered the event'

Does anyone have any workaround recommendations because obviously they aren't treating this as a priority. 

+1 +1 +1 +1 +!

We use a gitlab integration. For each commit i'm mentioning an issue in, I get one notification on the website, plus one on my smartphone '^^ 

It would be extremely beneficial to have this feature available for other types of automations as well. I have multiple rules that trigger status transitions for issues, but I do not need notifications to be sent when these rules are executed. In essence, we need an option to "Disable Jira notifications when specific Automation rules are executed."

+1

+1 would be awesome

+1 

+1 this would be really valuable for our use case, as we have rules to clone issues monthly, preserving the assignee - this results in high volumes of  emails to the assignees on the days the rules trigger. 

Isn't the workaround (at least for user activated automations) to change the Actor from "Automation for Jira" to "User who triggered the event"?

+1

Please do this already.