Guide
The free way to write your own comment notification, and what it costs you.
Jira Automation is included in your plan and it can send email. If the notification scheme cannot express what you want — notify a shared inbox, notify only on high priority, notify a person who is not in Jira — this is the next thing to reach for, before you pay anybody for anything.
Project settings → Automation → Create rule.
This fires on every new comment on issues in scope for the rule.
This is the part the notification scheme cannot do. Restrict by priority, issue type, label, or by what the comment says.
Choose recipients — a role, a field such as Assignee or Reporter, or a literal address.
Use smart values to pull in the issue and the comment. The ones you will want:
| Smart value | Gives you |
|---|---|
{{issue.key}} | The issue key |
{{issue.summary}} | The issue title |
{{issue.url}} | A link to the issue |
{{comment.body}} | The comment text |
{{comment.author.displayName}} | Who wrote it |
{{issue.assignee.displayName}} | Who it is assigned to |
Turn the rule on, comment on an issue as somebody other than the rule actor, and check the audit log under the rule if nothing arrives.
Executions are metered. Automation rules draw on a monthly execution allowance set by your Jira plan. A rule on Issue commented fires on every comment in scope, which on a busy project is the fastest way to spend that allowance. Check your usage under Automation before pointing the rule at every project you own.
Comment formatting is awkward. {{comment.body}} does not carry the commenter’s formatting into an HTML email cleanly. Bullet lists, code blocks, and mentions tend to arrive flattened or with markup showing.
The sender is Atlassian, not you. The mail goes out through Atlassian’s infrastructure from a Jira address. For an internal team that is fine. For anything a customer reads, it is not the impression you want.
Rules break silently. A changed field, a renamed role, a project moved to a different scheme — the rule stops doing what you assumed and nothing tells you. The audit log has the answer, but only if you think to look.
If you find yourself maintaining a comment-email rule across several projects, watching the execution count, and still unhappy with how the message looks, that is the point where a purpose-built app earns its price.
Comment Alerts for Jira emails the assignee and reporter on a new comment, with your wording, from your own address, through your own Resend account — so the comment’s formatting survives, the sender is you, nothing is metered against your automation allowance, and every attempt is logged where an administrator can read it.
The honest catch is the same one as always: it needs a Resend account and a verified sending domain before it delivers to anybody. If you cannot add a DNS record, build the automation rule instead.