Automatic Jira tickets from Sentry, without the Business plan
Sentry's Jira integration can create Jira issues from errors automatically — but automatic issue creation is only included on Sentry's Business and Enterprise plans. Sentry's own documentation puts it plainly: "Automatic issue management is available to organizations on Business and Enterprise plans," while "manual issue management is available to organizations on Team, Business, and Enterprise plans" (docs.sentry.io). On the Team plan, that means someone has to click "Create Jira issue" on every error that matters — and the errors nobody clicks on get missed.
This page lays out the realistic options for a team on the Sentry Team plan that wants every new Sentry issue to become a Jira ticket automatically — including the trade-offs of each.
What's gated, exactly
Per Sentry's Jira integration docs (as of October 2026):
- Manual issue creation and linking: Team, Business and Enterprise plans.
- Issue sync (comments, assignees, status, both directions): Team, Business and Enterprise plans.
- Automatic issue creation via alert rules: Business and Enterprise only.
- Required custom fields: "We don't support custom required fields" — on any plan.
So the Team plan (from $26/month on sentry.io's published pricing, October 2026) gives you everything except the "automatic" part — which is the part that stops errors from being missed.
Your options, honestly compared
- Upgrade to Sentry Business. The native route. Automatic issue management and alert-rule ticket creation work out of the box. The trade-off is cost: Business pricing is per-plan on sentry.io/pricing, and if automatic Jira tickets are the only Business feature you need, you're paying for a lot you won't use. Note that required custom fields remain unsupported even on Business.
- Keep clicking manually. Free. Works. Relies on a human noticing every error worth tracking — which is exactly the failure mode automatic ticketing exists to remove.
- A no-code automation platform (Make, Zapier, n8n). Make, for example, markets "automated ticket creation" from Sentry errors to Jira (make.com/en/integrations/sentry). This genuinely works, and it's flexible. The trade-offs: a separate subscription and another vendor between your error data and your tracker, plus you build and maintain deduplication, regression-reopening and two-way status sync yourself — scenario by scenario.
- DIY with Jira Automation incoming webhooks. Point a Sentry webhook or alert at a Jira Automation rule. No extra vendor, no extra subscription. But the rule starts from raw JSON: deduplication, reopening regressed issues, resolving in Sentry when Jira closes — all of it is yours to build and debug, against Jira Automation's rule-run limits.
- A dedicated Marketplace app. Purpose-built apps (ours is one of several — search "Sentry" on the Atlassian Marketplace) handle creation, dedupe, regression reopening and status sync as a product, installed from the Marketplace and billed through Atlassian alongside Jira.
How Sentry Bridge does it
Sentry Bridge for Jira connects to a Sentry internal integration — included on the Team plan ("API & third-party integrations" is a listed Team-plan feature on sentry.io/pricing) — so it doesn't depend on the Business-plan alert actions at all. From there:
- Every new Sentry issue in a mapped project opens one Jira work item: title, culprit, environment, release, level, counts, a stack excerpt and a link back to Sentry. Repeat events never open duplicates.
- Resolving in Sentry moves the ticket to Done; moving the ticket to Done resolves the Sentry issue. Regressions reopen the existing ticket with a comment instead of leaving it closed.
- Required custom fields are filled from templates like
customfield_10051={{environment}}— the thing Sentry's own integration doesn't do on any plan. - It's built on Atlassian Forge: credentials sit in Forge's encrypted secret storage, the settings pages are Atlassian-hosted (no third-party scripts for an ad blocker to break), and the only outside service the app talks to is Sentry itself.
Setup is about ten minutes — see the setup guide. The free Developer plan is the one Sentry plan this can't help with: Sentry doesn't include integrations there.
Quick answers
- Does this work on the Sentry Team plan? Yes — that's the point. It uses a Sentry internal integration, which the Team plan includes.
- Does it work on Sentry's free Developer plan? No. Sentry doesn't include integrations on the free plan.
- Self-hosted Sentry? Not in v1 — sentry.io and regional hosts (like
de.sentry.io) only. - When is it available? Sentry Bridge is coming soon to the Atlassian Marketplace — request early access to hear when it lands.
Sentry is a trademark of Functional Software, Inc. Jira and Atlassian are trademarks of Atlassian. Integration Yard is not affiliated with or endorsed by either company.