-
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
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[AUTO-602] Option to suppress in-product / in-app notifications caused by Automation for Jira actions
+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 ;-(
Upvote +1
We use Automation for Jira to log info in the comments of an issue. Because this sends a notification every time, it causes the important comments to get lost in the mix.
At the very least add the ability to set statuses within the "Edit Issue Fields" action so we can uncheck the "Send notifications" box.
We need to be able to remove these from notifications and suppress visibility of entries in the history tab as well
We also have a lot of customers who really annoys with such behaviour - it would be great to have option to disable notifications from Automation user.
From my point of view, as AUtomations is a system part of Jira, it should have possibility to do silent updates and not yell about any change
We're using the Data Server version, and I have to say that while I was very excited to finally get Project Automation, the senseless e-mail notifications make it my life (as the automation creator) unmanageable. I've ensured that all of the automation scripts have the e-mail notification unchecked, however I'm the only "Owner" and "Actor" and have no other way to suppress these.
Please reconsider Atlassian. Our team needs this as well. Too much notification noise from automations is significantly reducing the value of the Notifications area.
Ongoing since 2020? This needs to be resolved ASAP. This completely defeats the purpose of being able to effectively manage notifications.
This limitation on my ability to optionally supress notifications on rules that were fired by an automation rule is ruining our customers experience...
We need to keep comments from a linked Jira Software story synced with the source Jira Service Management issue so that whichever one is viewed (post escalation) has the same narrative. It seems repetitive i appreciate but this guarantees the whole picture is present for all participants whether our staff members, or the client. The rule i have used the causes/caused by link and if a comment is left on a it is copied to b and vice versa. The issue I have is each copy causes a duplication on the notification as I cant turn off the notification (that would break required functionality where there is no linked issue!) so the customer gets two updates for essentially the same comment.
Because of this they are drowning in emails (having come from a platform that was reliant on manual email updates previously so used to a much lower level) and all too often, due to the volume that I can't control easily, they just ignore the emails which results in a poorer interaction and reduced responses on the very emails we want them to respond to.
Having an option when you setup a rule to suppress the notification if a comment is added by Jira Automation would make the world of difference and I am flabbergasted that Atlassian have assigned this a "Not being considered" status when it clearly has a demand and a useful function. Please reconsider this, now!
I can't believe this still has not been resolved. What is the point of having notifyUsers query param in the API when it still notifies the user through notification center?
This is crucial. I use the notification center in my daily work. Having it filled with spam notices from Jira automation is hugely detrimental. It means I either can't use automations, or I can't use the notification center. Why on Earth would you let the notification center get filled with spam from automations that are integral to making the application work properly?
This is so important - what's the point of push notifications if the list is perpetually full of junk?
It's not feasible to use once you start creating automations. The feature may as well not exist.
We are requesting the implementation of the feature as the notifications toolbar are now serves no practical value as it's flooded with Jira Automation notifications.
We've quite a few automations in our Jira Instance and I've got a lot of complains from the users regarding the notifications.
We are also eager to implement this feature. Thank you for your consideration.
Dear Team,
This implementation is crucial, the team have start looking to move to a new tool instead of Jira.
Users are getting spam by emails and mobile notification from Jira Automation.
Because of Automation Jira Notifications, the top right button / notification menu is no longer being used by our team but it is good and we prefer to be able to use it
Adding another comment since I see they marked this one as "not being considered."
I've had multiple teams throughout our Jira projects complain about how much noise is generated from the automation account. Users NEED a way to filter out "Automation for Jira." I've had to design custom slack notification channels just because it makes the "Jira Notification" app within slack completely useless, as it's flooded with noise.
Atlassian, PLEASE reconsider this feature request.
Automation for Jira causes alarm fatigue and there's no good way to prevent 80%+ of notifications being irrelevant. Please consider implementing a solution to this problem!
The ability to turn the Automation notification in the desktop notification area (not just the email) is needed, folks. It creates noise that takes away from the usefulness of that area.
We need to sync comments between linked issues so that whichever side of the fence the issue lives the narrative is present - it would be ideal if we can stem email notifications on the linked updated issues comment action - at the moment we get one notification for each item updated so it is creating duplication that we should be able to control. Of course I cant turn off issue notifications when a comment is left in JSM as that then breaks the notification scheme. Would be really grateful if the option to supress emails on a for linked issue comment was made available to reduce the noise for our users!
Interesting to note that this important potential fix has been put in the bin. As usual, Atlassian picks the direction it wants to go without considering the end users.
I couldn't be more agreeable to the above - excessive and unnecessary notifications
Just got Jira Service Management and can't believe this isn't an option to turn off. Why would we want all those notifications? Just notify if there is a failing automation.
We use a ton of automation in our workflow due to business requirements. As a result, our notification feed is packed with useless automation updates. We should be able to filter these out in some way.
Over 84 people have voted for this. It should be re-considered. Please Atlassian. Thanks!
I cannot set a 'pull request created' trigger's actor to 'User who triggered the event' (which would allow individual users to block email notifications for when 'You make changes to the issue') because apparently 'The selected trigger requires the actor to be set to a user'. And, I can't just block automation emails outright. This is generating a lot of spam! Please reconsider this issue!
I agree, I'd like to see the "Send Notifications" checkbox added to more actions than just Edit Issue, particularly Transition Issue. Here's an example:
When a comment is added → update the status
This is an automation straight from the library, and in our case swaps statuses between "Waiting for Customer" and "In Progress" when an agent or customer comments on an issue, respectively.
One suggested workaround is to change the automation actor from Automation for Jira to 'User who triggered the event'. However customers don't have permission to edit/transition statuses, so this automation would fail half the time.
The other suggested workaround I've seen is to build special transitions purely for automations, and to hide these from users. What a ridiculous and needlessly complicated/fragile 'solution'.
We're new to using Jira (having come from SysAid), and honestly everything relating to emails has just been an absolute mess. A few weeks in and the email signatures becoming comments and cluttering the issue page is already incredibly frustrating.
The amount of noise Automation for Jira generates in Slack messages (which are not threaded) and notifications on Jira is ridiculous.
We do not need to know if Automation for Jira edited an issue, we set up the rule, we know it's going to do it.
Not only have you updated the notification bell making it almost useless to use
Bring the old view back.... was nothing wrong with it...... stop updating stuff that isn't broken and start by fixing the issues we are highlighting to you Atlassian!!
P.S I have 1 automation rule that updates 7 custom fields and i still get spammed by each custom field update .
+1