At the beginning of each month, people are emailing me asking questions on why I keep adding tickets to their queue. I didn't realize that when an issue is cloned, it will email the previous clone's assignee that a new ticket is ready for them. I was wondering if there was a way to prevent the previous assignee from getting emails from Jira based on my clone?
from my experience this is basically intended behaviour. You mentioned "beginning of each" month so it looks like the clone is done programmatically on your side.
Would you like to describe the use case any further so there can be alternative suggestions from Community members on how to deal with it?
When it must be a clone one idea would be to change the assignee to a different value (a null-user or something - but you would double check if you are sending to reporter, watcher or any other user-related custom field also).
With a specialized App from marketplace you could also clone to a different Jira-Project which has no notification scheme assigned to it.
Speaking of the notification scheme I want to add that it would be possible, at least in theory, so configure it before the clone so right after that action is no mail sent to them. This would imply switching back to the old notification scheme afterwards and taking care for fields like assignee, reporter, watcher and so on.
Without details it is hard to say anything thorough but it seems the best approach in this case is to re-work the process somehow.
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