Guide
Three ways to do it in Jira Cloud, and the honest limits of each.
Jira Cloud already emails people when a comment is added. Most of the time the complaint is not that nothing arrives — it is that the wrong people get it, or that the message is unreadable, or that it stopped arriving and nobody knows why. Each of those has a different fix.
Start by working out which one you actually have.
Every Jira project has a notification scheme: a list of events, and for each event, who gets told. Issue Commented is one of those events.
Project settings → Notifications. You will see the scheme the project uses and the recipients for each event.
It lists who is notified — typically Current Assignee, Reporter, All Watchers, and sometimes a project role or a whole group.
You need Jira administrator rights, and the scheme is usually shared with other projects. Changing it changes those projects too, so make a copy first if you are not sure.
This handles the majority of cases and costs nothing. If your problem is too many people are being emailed, this is where you fix it — see notifying only the assignee and reporter.
Jira Automation can watch for a comment and send an email you write yourself. Project settings → Automation → Create rule, trigger Issue commented, action Send email.
This is the right tool when you want unusual routing: notify a specific person only when a keyword appears, only on one issue type, only when the priority is high. It is genuinely powerful and it is included in your Jira plan.
Its limits are worth knowing before you build on it. Automation rules consume a monthly execution allowance that depends on your Jira plan, and a busy project can spend it quickly. Formatting the comment body inside an automation email is fiddly. And a rule is a piece of configuration somebody has to maintain — rules quietly break, and when they do, nothing tells you.
There is a fuller walkthrough in sending comment emails with an automation rule, including what it looks like when it goes wrong.
An app makes sense when you want the message itself to be yours: your wording, your subject line, your sender address, going out through your own email account rather than Atlassian’s — and a log showing what was sent and to whom.
Comment Alerts for Jira does exactly that and nothing else. On a new comment it emails the issue’s assignee and reporter — those two people, no one else, and both must be Jira users with an address the app can read — using a subject and body you write, sent through your own Resend account. Every attempt is recorded on the settings page with its result, so a message that never arrived shows up with a reason instead of vanishing.
Be aware of what it asks of you in return: you need a Resend account and a verified sending domain before it will deliver to anyone. That is a DNS change and ten minutes of setup. If nobody at your company can add a DNS record, one of the two free options above will serve you better.
| If your problem is… | Use |
|---|---|
| Too many people are notified | The notification scheme |
| Nobody is notified | The notification scheme, then personal settings |
| Only notify in certain conditions | An automation rule |
| The email needs to say something different | An app |
| Mail must reach a shared inbox or a non-Jira address | An automation rule |
| You need proof of what was sent | An app |
Two of those three cost nothing. If one of them solves your problem, use it.