Balancing Jira Issue Watchers to Avoid Duplicate Email Alerts

The core issue is that duplicate emails stem from the same user matching multiple notification rules across different schemes or events. Jira deduplicates only within a single event — if a user appears via both a "Watchers" role and an explicit group in the same event, they get one email. But if two separate events (e.g., "Issue Transitioned" and a custom "Status Changed") each notify the same user, two emails are sent.

Reliable pattern: define one shared notification scheme per project category, map each workflow transition to a single custom event (via a "Fire Custom Event" post-function placed after the status update), and in that event notify only "Current Assignee", "Reporter", and the "Watchers" role. Avoid adding both the role and a separate user/group rule for the same transition.

To verify, enable DEBUG logging for com.atlassian.jira.mail (Data Center) or request mail logs from Atlassian Support (Cloud), trigger the transition, and count RCPT TO lines per recipient. The Notification Helper (Administration → System → Notification Helper) also previews which events will notify a test user.