Email in, issues out, no mailbox handed over.
Mail to an address you own becomes a Jira issue; a reply becomes a comment on it, with the quoted history stripped and the files attached. Your own mail routing forwards each message in — the app never holds a mailbox.
The real module, running right here.
Working software on sample data — the same interface that renders inside Jira. It plays a short tour when it comes into view; click anywhere in it to take over.
The email you write is turned into a real message and handed to the app's own code: the same parser and the same pipeline that run inside Jira decide whether to ignore it, thread it onto an earlier issue, strip the quoted history, create the issue and attach the file. Only Jira and the mail log are stand-ins, held in this page. Installed, your own mail routing forwards each message to the channel's private address; the app has no mailbox and sends no email.
Built for the job, not the brochure.
Issues and comments
A new message becomes an issue; a reply threads onto the issue it answers, by its mail headers or the issue key in the subject.
Only the new part
Quoted history is stripped from replies, and files arrive as attachments on the issue.
Bring your own routing
Cloudflare Email Routing, Postmark, SendGrid, Mailgun, or anything that can make an HTTPS POST.
Guards on the door
Allowed and blocked senders, a per-sender limit and an optional SPF/DKIM check.
Noise ignored
Out-of-office replies, bounces and mailing-list mail are ignored before they reach Jira.
A log that explains itself
Every message that reaches the channel is listed, including the ones it ignored, and why.
Three steps from install to answer.
Create a channel
Choose the project, what new mail becomes, and who may send. The channel gets a private address.
Point your mail at it
Forward your support address with Cloudflare, Postmark, SendGrid or Mailgun.
Work it in Jira
Issues arrive with the sender matched to a Jira user where one exists. People are notified the way Jira always notifies them.
Inside Atlassian, with Jira’s rules.
The app never holds a mailbox and never sends email. Your mail routing forwards each message to a channel’s private address, and everything after that happens on Atlassian’s compute. What “never leaves your instance” means →
- The private address is shown only to project admins; make a new one if it leaks
- If Jira can’t take a message, the Cloudflare worker refuses it, so the sender’s server returns it — nothing disappears silently
- Mailgun sends files as form uploads the app can’t read; the log says when files were left out
- Replies from Jira go out as Jira’s own notifications
Straight answers.
How does email reach Jira if the app has no mailbox?
Your own mail routing forwards it. Point Cloudflare Email Routing, Postmark, SendGrid, Mailgun — or anything that can make an HTTPS request — at a channel’s private address, and each message becomes an issue, or a comment when it answers an earlier one.
Which messages are ignored?
Out-of-office replies, bounces and mailing-list mail, senders on the blocked list or missing from an allow-list, and senders over the per-sender limit. The mail log lists every one of them with the reason.
Do attachments come through?
Yes with Cloudflare, Postmark, and SendGrid’s raw mode. Mailgun forwards files as form uploads the app can’t read; the mail still arrives and the log says what was left out.
Guides and articles.
Turn a support address into Jira issues with Cloudflare Email Routing
Forward a support address on your own domain into Jira, so each new message becomes an issue and each reply lands as a comment — without giving any app a mailbox.
Read the guide →See Claude Code spend per person, team and Jira issue
Point Claude Code’s own telemetry and a GitHub webhook at Workforce Intelligence, and see what AI coding costs — per person, per team, and per Jira issue it helped build.
Read the guide →Earned value for Jira projects, in plain English
Spent 48% of the budget — is that good? Earned value answers by comparing what you spent with what that money was supposed to buy. Here is the whole idea, with one worked example.
Read the guide →Be first in when it opens.
One email when early access opens. Nothing else — no newsletter, no drip sequence, and the list isn't shared with anyone.
Early access members get the first year at launch pricing, locked.
Your address is stored with Resend, the email service that will send that one email.