-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
Currently, we can only suppress Email notifications for the Edit Issue action performed by automation or Jira. However, we still receive a notification on the instance:
Suggested workaround
Provide an option to suppress email notifications as well as the Notifications on the instance triggered due to actions performed by Automation or Jira, including app notifications, i.e. Slack notifications.
- is duplicated by
-
- Closed
- relates to
-
- Gathering Interest
-
- Gathering Interest
-
- Future Consideration
[AUTO-602] Option to suppress in-product / in-app notifications caused by Automation for Jira actions
I create a ticket and get 5 AJ notifications one for each automation, If I create it and resolve it only with little to no edits, I get 7+ (one for each edit comment, ext). I manage tens of tickets in a day, that's hundreds of notifications every day.
I don't need notifications that I just did something like created a ticket, edited a ticket, commented on that ticket, resolved the ticket or closed it, or anything else "I" do to it; I did that, trust me I know! I need notifications when others do things.
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.
Fellas, the interest has been gathered.
Let's move this along please
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.
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.
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
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.
this is causing lot of unwanted additional work for the team..needs to be addressed ASAP
+1 - I don't need our engineers spammed with rules I've added for adminstrative/management reasons - enable this asap, please!
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.
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 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"?
This seems like such an easy win. If you use any automations within your Jira setup then the notifications are essentially useless because it is filled with spam.
add an option in the api too. when my app do a massive change, notifications are not usable
+1 - being unable to modify notifications from automations is a major oversight
lack of this feature makes Jira notifications pretty useless if you also use automations. plz add
+1
4 years... How did the product owners not see this coming is beyond me.
Isn't the whole point of automations to reduce the workload of users? We need to get updates on changes to issues, but not from the automations, which are spamming inboxes.
Team Atlassian... There is a lot of love in the community for you guys.
However... 600 votes and almost 4 years.
@Tanguy_Crusson: Surely this merits a move to the 'Next' part of the RoadMap? 🙏🏻
+ 1 - Very important to us, as we do run scheduled issue updates which do not need to inform people involved.
this is so painful that we can't turn these notifications off.... a pretty obvious UX issue that has been around for years? /facepalm
We use Automation for Jira to populate some hidden fields for reporting only and we intentionally mark the "Send notifications?" to false in the Edit action, but the Slack app is still sending notifications for our users...
It's weird that A4J consider only emails as notifications ... there are a lot of others ways that a user can be notified and we need to have the ability to suppress them when needed.
Its ok - Atlassian have solved this. The days of too many notifications are soon to be gone. because you'll be limited to only 5,000 automation runs a month.... there, fixed it.
The sheer number of automation notifications is making it very hard to manage my workflow. I do not need to be notified that a mail has been sent, but being told a mail has not been sent would be more useful. Notifications of client responses, cases being assigned to me and internal notes can easily get lost.
Also, when I click on a notification for a client response, an internal note a case being added to my pool, it goes from being unread to read, but this isn't the case for automation notifications, which again, can make it difficult to keep on top of my workflow.
When you have quite the few automations set up, the notifications form the Automation for Jira actions render the notifications tab useless as it gets pretty crowded. The ability to mute this notifications would be pretty handy
I agree this would be useful to suppress notifications for comments that are added through automation. Too many notifications can make it easy to miss end-user responses.
Having the ability for the automation NOT to notify is essential in many use cases.
Another way to handle this could be to have an option as part of the custom field itself (e.g. boolean flag "can generate a notification"). Then you can turn this on or off per field.
But having the logic on the automation rule would be most logical.
I also don't understand why this setting is not considerable. The notification feature becomes more of a risk than a used tool...
+1. Too many automated notifications. Notifications are cluttered and useless.
Hi Atlassian Product managers, Please help to consider this. The in app notifications in Jira becomes useless if it will get flooded with irrelevant automation spam notifications. These spam notifications lead important and critical notifications to get buried and missed.
+1 - Extremely important functionality. Automation is great tool but a constant complaint from my users is that the Automation notifications in Jira and on the mobile app.
How else can we support getting more REST APIs available so the Automation team can consider this? Upvote https://jira.atlassian.com/browse/JRACLOUD-73887 ?
Hello Atlassian Developer,
We have a serious problem with this notification, my user have complaint about the notifications sent from Automation for Jira.
One case happened with one of my user because of this notification email, there was one important email from our customer for my user, the email was sit in the middle of bunch of "Automation for Jira" emails for almost two weeks, my user didn't aware of the customer's email until was called by the customer why she didn't response the email.
We may think of this notification would not causing any serious issue, but it is not, it can become a big problem that causes huge losses for company just because of this notification emails.
I think the audit logs are enough, the notifications sent to users are most of the time unusable for user, it is mostly useful for administrator.
Please consider this and lets make Jira software much better and better.
Thanks!
+1, not only Disable Email notification, but also Disable Notification to Microsoft Teams Integration and Jira app as well, when Automation changes the status on a ticket I get a notification from my PC and my phone on all 3 of the bellow:
- Outlook
- Teams
- Jira app
It gets a little noisy at times!
+1 Critical notifications are being missed due to automation spam.
@Matthias, it looks like it was changed to "Not being considered" directly after this comment:
From an Automation point of view, we're blocked until more APIs become available in Jira (see linked tickets). We'll take a look again when the APIs are available
So it looks like we need to get the ticket below upvoted and implemented in order for this ticket to be re-considered.
This issue has garnered the second-highest number of votes on the "Automation for Cloud" board. In order to better comprehend the decision-making process, could you please provide insight into why this issue is currently marked as "not being considered"? Thank you.
This needs a bump in priority. 90% of my Jira notifications consist of Automation notifications. Making notifications unusable ;-(
Currently I just end up ignoring in-app notifications. I'm sure Atlassian would prefer we engage with this core feature rather than ignore it as many are forced to do.
Please make this basic feature useful and allow us to filter out spam notifications. I'd be content with an ability to set an automation to notify the end-user only.