Documentation
Email the assignee and reporter the moment someone comments on an issue.
When someone comments on a Jira issue, Comment Alerts emails that issue’s assignee and reporter. The message goes out through your own email account, using wording you control, and every attempt is recorded so an administrator can see exactly what was sent.
It ships with a single rule: new comment → assignee and reporter → every project. There are no per-project rules, no other trigger events, and no recipient picker yet. If one of those is what you need, get in touch — what people ask for is what decides the next release.
You need a Resend account. The free tier is enough to evaluate the app. Step 2 is the one that catches people out, so do not skip it.
Sign up at resend.com.
In Resend, open Domains, add the domain you want mail to come from, and add the DNS records it shows you. Wait until it reads as verified before continuing.
Resend → API Keys → Create. Copy it now — Resend will not show it to you again.
Settings → Apps → Email notifications. You need to be a Jira administrator.
Use an address on the domain you verified, such as jira@yourcompany.com. Paste the API key and choose Save settings. The key is encrypted and is never displayed again.
Enter your own address under Send a test. If it arrives, you are finished. The next comment on any issue will notify its assignee and reporter.
Resend gives new accounts a shared sender on resend.dev. It only delivers to the address that owns the Resend account. Mail to anyone else is accepted and then silently discarded — the app reports success, the delivery log says sent, and nothing arrives.
The app warns you when it sees a resend.dev From address. Verify your own domain and the warning clears.
The subject and body are yours to write. Wrap a placeholder in double braces to insert its value with HTML escaped, or triple braces to insert it raw — use triple braces for comment.body so the commenter’s formatting survives.
| Placeholder | Value |
|---|---|
issue.key | The issue key, such as ENG-412 |
issue.summary | The issue title |
issue.description | The issue description |
issue.status | Status name, such as In Progress |
issue.priority | Priority name |
issue.project | Project name |
issue.assignee | Assignee display name, or Unassigned |
issue.reporter | Reporter display name |
issue.url | A link straight to the issue |
comment.body | The comment, as HTML. Use triple braces. |
comment.author | Who wrote the comment |
actor.name | Who triggered the event |
Use Preview to render your template against a sample issue before anyone receives it. A placeholder with no value renders as nothing and is listed under the preview, so a typo shows up rather than going out silently.
Almost always the sending domain. If your From address ends in resend.dev, only the address that owns the Resend account can receive anything. Verify your own domain and use an address on it.
Open Settings → Apps → Email notifications and check Recent sends. A row reading skipped — no resolvable recipients means neither the assignee nor the reporter has an email address the app can read. An issue with no assignee and no reporter produces nothing.
It is administrator-only, and it lives in Jira admin settings rather than the main Apps menu: the gear icon → Apps → Email notifications.
Email support@signalpostapps.com with the issue key and the time, and we will look at the delivery log.
Longer write-ups on notifying people about Jira comments, including the ways to do it without this app.