Guide
Stopping Jira from emailing half the project every time somebody replies.
The usual cause is not a bug. It is that your notification scheme lists more recipients for Issue Commented than anyone intended — often All Watchers, which grows quietly, or a project role that has picked up most of the company.
Project settings → Notifications. The scheme name is at the top. Note it — the next step will tell you whether other projects share it.
Jira settings → Issues → Notification schemes. The list shows how many projects use each one. If it is more than one, copy the scheme first and associate the copy with your project, or you will change notifications for teams who did not ask you to.
Remove the recipients you do not want. To notify only the two people who care most, leave Current Assignee and Reporter and remove the rest — particularly All Watchers, Project Role and any group entries.
Comment on an issue as somebody else and confirm who receives it. Do not test by commenting as yourself: Jira does not notify you of your own actions unless you have turned that on in your personal settings.
Anyone who has ever been mentioned on, assigned to, or interested in an issue may be watching it. All Watchers looks harmless on the scheme and turns into twenty people on a long-running ticket. Removing it is the single change that quiets most noisy projects.
Someone still gets nothing. Check their personal notification settings, then check that they have permission to browse the project — Jira will not email a person about an issue they cannot see, no matter what the scheme says.
The email is still ugly. Jira Cloud does not allow administrators to edit notification templates. If the wording itself is the problem — because the recipients are clients, or contractors, or anybody who should not be reading Jira’s house style — the scheme cannot help you and no amount of configuration will.
You need to know it was delivered. Jira keeps no record you can inspect. When somebody insists they never got the email, there is nothing to check.
That last group of problems is what Comment Alerts for Jira is for. It emails the issue’s assignee and reporter on a new comment, with a subject and body you write yourself, sent from your own address through your own Resend account, and it records every attempt so you can see what went out and to whom.
It needs a Resend account with a verified sending domain — a DNS record and about ten minutes. If your problem is only too many recipients, the free fix above is the better one and you should stop here.