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
Glass of Gold for person who can help here : )
What you would need to do is:
personally I would not recommend this for several reasons:
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.
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.
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).
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)
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events