keelapps

keelapps/Mail Templates

For the stakeholders Jira never emails

Jira notifies watchers. The people who most need to know usually are not watchers.

A compliance contact, a support group, the account manager who owns the customer relationship — none of them watch the issue, so Jira sends them nothing, and someone ends up forwarding mail by hand. Mail Templates sends a structured, templated message to recipients you name, on the events you choose, delivered by Jira's own notification service. Nothing leaves Atlassian.

Coming to the Atlassian Marketplace Zero egress. No external mail server, no vendor copy of your issue data.

This is an additional notification channel, not a replacement for Jira's own. Jira keeps sending whatever its notification scheme is configured to send; Mail Templates adds a message on top, which is exactly why it suits people who would otherwise get nothing. If you want to stop a duplicate for someone who already gets Jira's mail, switch that event off in the project's notification scheme — and check what else shares that scheme first.

What it does

Recipients you choose

Reporter, assignee, watchers, voters, named people or a Jira group — set per rule. Not a forward of the watcher list, which is the thing that failed to reach these people in the first place.

Three events, three templates

Issue created, status changed and comment added, each with its own subject, body and recipient set. Turn on only the ones a project actually wants.

Templates that fill themselves in

Nineteen issue fields interpolate into subject and body — key, summary, status, assignee, priority, the transition that just happened. One template serves every issue in the project.

A preview that is the real renderer

The preview under the editor is produced by the same code that renders the mail that gets sent, so what you approve is what goes out.

Every send accounted for

A per-project log records each event handled — including the ones that sent nothing, and why. "Why was there no email" always has an answer.

Delivered by Jira itself

Built on Forge with no external network access. Mail goes out through Jira's own notification endpoint, which is what earns the Runs on Atlassian badge — something a Connect app on a vendor's server cannot get.

A release notification, end to end

  1. The rule is written once

    On the Releases project, a project admin turns on "status changed", writes a subject of [{{project.key}}] {{issue.key}} — {{issue.summary}}, and picks the recipients: the reporter, plus the customer-success group.

  2. Someone moves an issue to Done

    Jira fires the event. The app matches it against the rule, reads only the fields the template references, and renders the message.

  3. The people who are not watchers get the mail

    Jira delivers it through its own notification service. Everyone on the list still has to be able to see the issue — Jira drops anyone who cannot, so the app can never widen access.

  4. The log says what happened

    The project's send log records the event, the result and the recipient count. Hourly caps bound the damage a bulk edit of 500 issues could do.

Against what you have today

Question Native Jira Connect notification apps Mail Templates
Can a non-watcher be notified? Add them as a watcher, or forward by hand Yes Yes, by rule
Templated subject and body with issue fields? Fixed Jira templates Yes Nineteen variables
Does issue data leave Atlassian? — Yes — vendor servers Never
Runs on Atlassian badge? — Structurally cannot Yes
Any write access to your issues? — Varies None — it can only send a notification
Can it replace Jira's own notifications? — Yes, by intercepting them No — Forge has no hook for that

That last row is the trade. Forge gives an app no way to suppress the mail Jira's own notification scheme already sent, so this is a channel that adds rather than replaces. The same constraint is what keeps every byte inside Atlassian — and there are things it therefore will never do: no attachments, no custom sender address, no unsubscribe management, no rich-text editor. All of those need egress or permissions this product exists to avoid.

Availability

Mail Templates is built and deployed on Atlassian Forge. It is going through Atlassian Marketplace review; this page will link to the listing as soon as it is live.

Licensing is handled by Atlassian. Sites with 10 users or fewer pay nothing at all; paid tiers are priced per user.

Questions, bug reports and feature requests: raise a support request.

Found a security issue? Please report it privately rather than in a public channel.