Have a review of the notification schemes set up for your system - the default is usually "notify reporter, assignee and watcher of all changes", but it's well worth reducing that to be a bit less noisy. (Especially the "issue updated", as that can happen for every minor change)
Not always a good move - you really do need to think it through.
I don't want to have to add watchers every time I create issues. Worse, I may not even have the right to do it. For example, what happens when a call for help comes in from an external user and it's automatically assigned to me because I'm the component lead? I want the assignee notification.
You may work through it and decide that watchers only will work for you. But watchers only fails for most users and you really need to think through each notification, not just bin them all.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs