Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×First, you need to identify who should stop getting the emails. The notification scheme controls what roles and groups get emails. Look at the post functions in the transition to see what notification is being executed, such as issue updated, and then at the notification scheme for that action. Whoever doesn't want to get notified can't be in a role or group that is setup to get notified in the notification scheme. JIRA doesn't have an exempt list for notifications.
Users can also control their own notification preferences via their profile. I'm reasonably sure that the User preferences will trump a notification scheme, so for conflicts, the User will win.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User preferences allow you to set the mail to text or html, and opt in/out of getting mails about changes you make (e.g. if the scheme says "notify assignee" and you're the assignee, when you make a change, you can opt out of getting the email to tell you what you've just done). That's all.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check the events the workflow fires as it goes into that status, and then check the notification scheme to see who the event triggers the emails to.
Then, think about removing that person from the notification. Or change the event being fired to something that won't notify them
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.