If your team runs Sentry on the Team plan and plans its work in Jira, you've probably gone looking for the alert action that turns a new Sentry issue into a Jira ticket. On Team, that action isn't there.

Sentry's Jira integration docs say it directly. Manual issue management is available on Team, Business and Enterprise. Automatic issue management is available on Business and Enterprise (Sentry docs). On Team you get manual creation and linking, plus issue sync for comments, assignees and status in both directions. What you don't get is the automatic part, where an alert rule opens the ticket for you.

That gap matters more than it sounds. A ticket only exists if somebody clicks "Create Jira issue" on the right error at the right time, and the errors nobody clicks on are the ones that get lost.

Here are the realistic options, with the trade-offs of each.

Option 1: Stay on Team and link issues by hand

This is free and it works. From a Sentry issue you create or link a Jira issue, and Sentry's sync keeps status, comments and assignees aligned once the two are linked.

The cost is attention. Someone has to triage Sentry, decide what deserves a ticket, and click. It's fine for a small team that already reviews Sentry every day. It breaks down when nobody owns triage that week.

Two smaller limits are worth knowing. Sentry's docs say, "We don't support custom required fields for the Jira integration," and they don't list a plan exception. So if your Jira project requires a field like Team or Component, the create form can get in your way. And because a person picks the Jira project and fields on each create, consistency depends on whoever clicked.

Option 2: Upgrade to Sentry Business

This is the native route. On Business, an issue alert can use "Create a Jira issue" as its action, and tickets open automatically.

The trade-off is price. On sentry.io's published pricing (November 2026, with default pre-paid data), Team is $26/month billed annually or $29/month billed monthly, and Business is $80/month billed annually or $89/month billed monthly, before usage. Business also brings other features, such as unlimited custom dashboards and advanced quota management. If you want those, upgrading is the right call. If automatic Jira tickets are the only Business feature you'd use, you're paying for a lot you won't touch.

Note that the required-custom-fields limit above still applies on Business.

Option 3: Sentry webhook into a Jira Automation rule

This is the DIY path, with no extra vendor. You create a Sentry internal integration (integrations are part of the Team plan) subscribed to issue webhooks. Sentry sends an event when an issue is created, resolved, assigned, archived or unresolved (Sentry webhook docs). You point it at a Jira Automation rule that uses the incoming-webhook trigger and a "Create issue" action.

It works, and for a single project with simple needs it can be enough. The rule starts from raw JSON, though, and everything past "create a ticket" is yours to build and debug:

  • Deduplication. You decide what stops a busy issue from opening a second ticket.
  • Regressions. When a resolved issue comes back, you need a rule that finds the old ticket and reopens it.
  • Reverse sync. Closing the Jira ticket won't resolve the Sentry issue unless you also build a Jira-to-Sentry call.
  • Usage limits. Each run counts toward your Jira Automation usage, and the limits depend on your Jira plan. Atlassian explains how usage is counted in How is your automation usage calculated. A noisy deploy can use up a lot of runs.

A no-code platform such as Make, Zapier or n8n sits in the same spot. It's more flexible, but you add another subscription and another vendor between your error data and your tracker, and you still own dedupe, reopening and status sync.

Option 4: A Marketplace app built for this

Several Jira apps on the Atlassian Marketplace handle Sentry-to-Jira creation as a product. Search "Sentry" there and compare what each one does with dedupe, sync direction, and the Sentry plans it supports. Disclosure: we build one of them, Autoticket for Sentry and Jira, and here's what it does, using only what our docs publish.

  • It works on Team. Autoticket connects through a Sentry internal integration, which the Team plan includes, so it doesn't depend on Business-plan alert actions. (It can't help on Sentry's free Developer plan, which doesn't include integrations, and self-hosted Sentry isn't supported.)
  • One ticket per issue. Every new Sentry issue in a mapped project opens one Jira work item with the title, culprit, environment, release, level, counts, a stack excerpt and a link back to Sentry. Repeat events don't open duplicates.
  • Noise filters. Each Jira project can set an environment allowlist and a minimum level, or switch to alert-rules-only mode so your Sentry alert conditions decide what becomes a ticket. Filtered events appear in the activity log with the reason.
  • Two-way status sync. Resolving, archiving or ignoring in Sentry moves the work item to a Done-category status. Moving the work item to Done resolves the Sentry issue. A regression reopens the existing ticket with a comment. Loop protection keeps the two sides from bouncing. If your workflow has no matching transition, Autoticket leaves the status alone and comments to say so (how sync works).
  • Required fields. Custom fields are filled from templates such as customfield_10051={{environment}}, which covers the case Sentry's integration doesn't.
  • Runs on Forge. Sync runs on Atlassian Forge, not on Jira Automation rules, so it doesn't consume Automation steps.

Pricing is free for Jira sites with 1–10 users. Above that it's USD $1 per user per month, counting all users on the site, billed through the Atlassian Marketplace (licensing details). Setup takes about ten minutes: create a Sentry internal integration, paste two values into Jira, and map a project (setup guide).

Which one should you pick?

  • You already review Sentry daily and file a handful of tickets a week: stay manual. It's free.
  • You want other Business features too, or your Jira site is large: upgrade. Per-user app pricing adds up on big sites, and for large Jira sites Business can be cheaper on price alone (side-by-side comparison).
  • You have one project, simple needs and someone who likes Automation rules: the webhook route is a good weekend project. Budget time for dedupe and regressions.
  • You want every new issue ticketed, with dedupe and two-way sync, while staying on Team: use a Marketplace app. Autoticket is here if you want to try ours.

If you've solved this a different way, tell me in the comments. I'm especially curious how people handle regressions in the webhook setup.

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.