Swich OFF the standard NOTIFICATIONS and build automation rules
Asked by Mateusz Janus:

Hello,

we receive so so many notifications on many organization levels. Is it possible to build below scenario:

- switch off sandard notifications on USER ID level

- create the automation like below

1. system check the ticket assignee

2. IF assignee = John Travolta then

a. send notification to John Travolta only when below fields are changed

- description

- assginee

- comments

Glass of Gold for person who can help here : )


Answers:
author: Jack Brickey
body: What you would need to do is:

1. turn off notifications for specific user - ensure your notification scheme does not include standard roles that the specific user is in, or remove this user from those roles/groups.
2. build automation rules for specific user - for every event where you wish to notify the user create a rule, e.g. issue created, issue transitioned etc. and add necessary conditions.

personally I would not recommend this for several reasons:

1. you are going to burn a lot of automations from your limited supply if you are on Standard
2. performance - automation is not free in this regard
3. Maintenance - could turn into a nightmare over time

You might consider an addon approach. I use JETI for certain special notification scenarios. There are other options as well like JEMH and more. Check the Marketplace.

comments: author: Mateusz Janus
body: thanks for reply.

Ok but what about simpler scenario then.

Send notifications for limited fields update? lets ignore the requirement regarding specific users.

I am JIRA CLOUD PREMIUM


author: Jack Brickey
body: So you are suggesting that you would disable all notifications and then simply add automation rules for certain fields being updated. Assuming I have that correct, sure you could have automation rules for that. You need to consider who you would want to send that to such as assignee, reporter, watchers etc. and build that into the automation. I think the key point here is will your automation rules replacing current notifications eventually grow into what the purpose of default notifications are meant to handle. If so then it becomes a maintenance challenge. That said, it is all speculation and you just need to consider what works best for you.


author: Mateusz Janus
body: thanks for warining. I am appreciate that.

I know that each user can switch off the notifications from USER ID level. So switching off the standard notification is not the problem on user level. Then the automation with selected fields triggers. How to build such a automation? the structure of blocks?

Lets back to scenario with JOHN travolta, I have only 2 stubborn users who wants to have that feature (HAVE TO HAVE).


author: Nic Brough -Adaptavist-
body: For a team-managed (next-gen) project, go to project settings -\> notifications and edit the list, removing all the ones you don't need

For a company-managed (classic) project, you'll need to edit the notification scheme, changing it to one that does not fire any emails

In both cases, you can then use automation rules - the simplest one would be the "When field value changes" -\> "send email to" (you'll need three for your case, each of your fields)