How to disable Automation Notifications

[Rasajna Meka]

If my automation is updating any field value in the issue , it consider this as issue updated and sends notification to the assignee and reporter . How to disable these notification as its spamming the reporter/assignee mail box

[Ignacio Pulgar · Accepted solution]

[Alex Koxaras _Relational_]

I had totally forgotten about this! @Ignacio Pulgar is right. Try this instead!

Good job Ignacio!

[Mike D_]

I don't see that option, what am I missing? 🤔

[Evn Tomeny [Appfire]]

Hi Rasajna,

If I'm understanding correctly, you're going to need to update the notification scheme. You have "Reporter" and "Assignee" receiving notifications for "Issue Updated". You can probably safely remove everyone from "Issue Updated", and make sure they're in "Issue Transitioned", "Issue Commented", or whatever other actions you want to notify them about.

Notifying on every single issue update can be spammy even before you start putting Automations in place. I generally don't send this notification, but ultimately it's up to you.

[Alex Koxaras _Relational_]

Hi @Rasajna Meka 

If your automation is updating any issue, then the "Issue Update" event is being fired, which it sends out notifications to all the people you have under "Issue Updated" notification.

Imo you can't block this if you are using Jira Automation, since there is no option not to send out notifications. If you were using an app like JMWE, then you would have this functionality.

[Hugh Kelley]

Is there any way to prevent the non-email notifications from cluttering up the UI? 

[Mike D_]

yes, what Hugh said! 👍

[Hugo Ludinant]

@Hugh Kelley @Mike D_ I had the same issue but found a workaround solution: you can remove the watchers before making changes, then restore them after the changes, dodging the notification from being sent!

In your rule, before making any changes, add a "Create variable" action to store the list of watcher accounts, for example:

Then a "Manage watchers" action to remove all existing watchers.

At this point, any change applied shouldn't send notifications.

Finally before the rule completes, add another "Manage watchers" action to restore the watchers using the smart value of the variable created earlier:

[Sweder Reuchlin]

Hi @Hugo Ludinant ,

Thank you for your explanation!

Could you please show the complete workaround showing where these actions are positioned in the rule. I still can't get it to work yet.

Thanks!

[Hugo Ludinant]

Hey @Sweder Reuchlin

Here is the whole setup:

Haven't tried with other changes than editing the parent of an issue, but in theory it'll work just as well in another context.

Hopefully this helps!

[Karin Kennergren]

B R I L L I A N T 

[Sweder Reuchlin]

Hi @Hugo Ludinant ,

Thank you for the screenshot. 

Unfortunately I still get a notification when the status of the parent is changed. This is how I have set it up:

Can you see if I am missing something?

Thanks!

[PatateNouille]

Hi @Sweder Reuchlin 

In my case I was modifying the issue that is getting transitioned, which is why I had the watchers actions on the main branch.

However I think that since you're modifying the parent of the transitioned issue, and not the issue itself, you'd need to put the actions on that branch.

Something like this:

I'm not sure if the actions would need to be adjusted, in theory the "Remove/Add watchers" actions will work, but there's a chance the smart value used in "Create Variable" picks the wrong issue.

I'd try with {{issue.watchers.accountId}} first, and if it doesn't work look for a potential special smart value to refer to the branch's issue?

[Sweder Reuchlin]

Hi @PatateNouille ,

Thanks for jumping in on the conversation.

That also didn't fix it unfortunately...

Is there another way to structure the rule so that I don't get notified every time?

Thanks!

[Hugo Ludinant]

Oh oops, it auto logged me into the wrong account haha, @PatateNouille is an alt.

Hm I'm not sure what can be done.

I tried to recreate the setup and it appears that changing the parent sends a Jira automation notification regardless of whether or not you're watching the issues affected?

Even manually removing myself from watching the sub-tasks, the parent, and even the epic, then triggering the rule, it still sends a notification.

Apparently when modifying a related issue, it always notifies the reporter. If I manually assign Automation for Jira as the reporter I stopped getting a notification, however doing so in the rule still doesn't work as it notifies it edited the issue's fields...

Only other trick I have left is to set the actor as the user who triggered the event.
At least this way I'm not getting a notification for what the rule does, but I assume other people might still get notified.

However this might be ok since I believe the notification would appear as if the user did the action themselves?

[Sweder Reuchlin]

Hi @Hugo Ludinant ,

This solved it (or at least I didn't get the notification anymore).

Thanks for your help, really appreciate it!

Best,

Sweder

[John Funk]

Hi Rasajna,

have them take themselves off from being watchers of the issue. Depending on your notification scheme, that should take care of it. But if they are watcher they will receive  everything.