- Sentry posts the webhook. Your alert rule fires and Sentry calls the URL you gave it. Nothing calls Sentry back.
- It checks the signature before it reads the body. HMAC-SHA256 over the exact bytes that arrived. If a request isn't signed, or is signed wrongly, it gets refused without ever being parsed.
- It strips the payload, queues it, and replies. Local variables, cookies, headers and extra context go first. The reply lands well inside Sentry's timeout, and the slow work happens afterwards.
- Your rules decide, then it writes to Jira. It matches on error level, and on Pro on environment and the rest, in order. An error it has seen before bumps that work item's count instead of opening a second one. On Pro, the delivery log records what happened and why.
Atlassian Forge · Jira Cloud
Triage for Jira
Sentry errors turn into Jira work items, on rules you write. It works on Sentry's free plan, because it never calls Sentry.
Install from the Marketplace Setup guide
- Jira sites under 10 users
- Free
- Sentry plan required
- Any, including free
- Data leaving Atlassian
- None
What lands in Jira
You get the error title, the culprit, level, environment, release, a slice of the stack
trace and a link back to Sentry. Two of those land in real Jira custom fields instead of
text in a description, so "Sentry Error Count" > 100 works in a board filter,
a dashboard gadget or a saved search.
Local variables, cookies, request headers and extra context get dropped before anything is stored. They hold whatever was in scope when the error fired, which in a real app means API keys and customer data. We rebuild stack frames from a short list of fields we know are safe to keep, so anything Sentry adds in future gets dropped by default instead of passed through by default.
Rules decide, and tell you what they decided
A rule starts with a Sentry organisation and project, then narrows by error level. On Pro it can also narrow by environment, how many times the error has fired, or a pattern in its title. Rules run in order and the first match wins. Each one picks the Jira project and work type it files into.
Send the same error a thousand times and you get one work item with a count on it. The count goes up, a comment records it, and nobody opens a second ticket.
That only helps with repeats of the same error, though, and repeats aren't what floods a backlog. A bad deploy throws hundreds of different errors in ten minutes, each with its own Sentry issue, each matching your rule. So every rule also gets an hourly cap, on by default. Anything it holds back stays in Sentry and creates a work item next time it fires.
On Pro, when a webhook doesn't become a work item, the delivery log tells you why: a rule filtered it, the cap held it back, it's already linked to a ticket you have, or nothing matched. In that last case you get what each rule objected to. Silent failure is the usual complaint about tools like this, and it's the thing we built this one to fix.
- Off in every Jira project until you switch it on. Most projects have nothing to do with Sentry, so Sentry detail never shows up in them.
- Attach a Sentry issue to a ticket you already have. When the bug report arrived before the error did, enrich that ticket instead of filing a duplicate.
- Resolve it in Sentry and Jira follows (Pro). A regression reopens the work item and leaves a comment explaining why.
- Self-hosted Sentry needs no extra setup. Your instance posts to the same URL sentry.io would, and you don't have to open any inbound path.
What it won't do
The app never calls Sentry. Sentry calls it. That's what keeps it running on the free Developer plan, what makes self-hosted instances painless, and what earns the Runs on Atlassian certification. It costs three things, and you should know them before you install rather than after.
- It only goes one way. Resolving a work item in Jira won't resolve the error in Sentry. Sentry to Jira, never the reverse.
- The event count is what this app has seen since you installed it, not Sentry's lifetime total for that issue. The webhook doesn't carry that number, and going to fetch it would mean calling Sentry.
- It can't see work items made by Sentry's own integration. If you use that integration's manual button too, link the two and deduplication takes care of the rest.
Pricing
Free for Jira sites of ten users or fewer. Above that it's priced per Jira seat, and the Marketplace will quote you the figure for your own seat count.
The free tier covers one Sentry organisation, three rules filtered by error level, manual linking, the issue panel and both custom fields. Pro adds unlimited organisations and rules, status sync from Sentry, the dashboard and delivery log, and the environment, occurrence-count and title filters.
Sentry's own auto-create needs their Business plan. This doesn't, so the comparison that matters isn't the price, it's that you keep whatever Sentry plan you're on.
Documentation
The setup guide walks through the Sentry and Jira sides in order, including the two steps people reliably miss. Troubleshooting starts from whatever you're staring at: find the message or the symptom, read what causes it.
Guide: How to automatically create Jira issues from Sentry errors