You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello Community,
I have a question to which someone I hope will have a solution or advice.
- A Jira Service Desk needs to create a series of SubTasks via automation once it is submitted = this works fine.
- The reporter receives the notification of the main Jira Desk submitted, which is great. They also receive notifications (yes plural) for all and each SubTasks automatically created and this is not good.
How to avoid that?
while the setup is not fully clear to me and I hope other users will chime in the first question that comes to mind is if in "Notification Scheme" the "reporter" could be listed for the "Issue created" event?
The behaviour of that setting comes close to what you are observing so it could make sense to check that first.
If that is not the case could you please be a bit more elaborate on what is configured on your end currently in terms of Automation rules and Notification schemes? Also the settings for notifications in Jira Service Management could be of interest then.
Regards,
Daniel
I second Daniel's thought:
if in "Notification Scheme" the "reporter" could be listed for the "Issue created" event
This is the first place I would check too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, it's clear and brief
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.