Integration Yard
Request early access
AutoticketDocsSecuritySupport Request early access

Setup guide: Autoticket for Sentry and Jira

Connecting Autoticket takes about ten minutes: install the app, create a Sentry internal integration, paste two values into Jira, and map a project. You need a Jira Cloud admin and a sentry.io organization on the Team, Business or Enterprise plan with permission to create integrations (Sentry org Owner or Manager). Sentry's free Developer plan doesn't include integrations, and self-hosted Sentry isn't supported in v1.

Step 1: Install the app and copy your webhook URL

  1. Install Autoticket for Sentry and Jira from the Atlassian Marketplace.
  2. Go to Jira settings (⚙) → Apps → Autoticket.
  3. Copy the Webhook URL shown at the top. It's unique to your site — treat it like a password and don't post it publicly.

Step 2: Create a Sentry internal integration

  1. In Sentry, open Settings → Developer Settings → Custom Integrations → Create New Integration.
  2. Choose Internal Integration and click Next.
  3. Name: Jira (Autoticket).
  4. Webhook URL: paste the URL from Step 1.
  5. Turn on Alert Rule Action (lets alert rules send to this integration).
  6. Permissions: Project: Read (not used by the app's own API calls, but kept here in case Sentry requires it to enable the issue webhook below) · Issue & Event: Read & Write (Write is needed so resolving in Jira can resolve in Sentry) · Organization: Read · everything else: No Access.
  7. Webhooks: tick issue (created, resolved, archived, unresolved) — not assigned, which the app ignores.
  8. Click Save Changes. On the saved integration page, copy the Client Secret, and under Tokens copy the auth token (create one if none is listed).

Step 3: Connect Jira to Sentry

  1. Back in Jira settings → Apps → Autoticket, enter:
    • Sentry organization slug — the part after sentry.io/organizations/ in your Sentry URL, or <slug>.sentry.io.
    • Sentry base URL — leave as https://sentry.io unless your org is on a regional host (for example https://de.sentry.io).
    • Client secret and Auth token from Step 2.
  2. Click Save, then Test Sentry connection. You should see your organization name.

Step 4: Map a Jira project

  1. Open the Jira project → Project settings → Autoticket (project admin or Jira admin).
  2. Turn on Create work items from mapped Sentry projects.
  3. Enter the Sentry project slug(s), for example backend, web-app.
  4. Pick the issue type (for example Bug) and, optionally, a default priority.
  5. Choose which events open work items: every new Sentry issue, or only alert rules; optionally limit by environment (for example production) and minimum level. Filtered events appear in the activity log with the reason.
  6. Choose the dedupe rule, and whether regressions reopen the work item.
  7. Optionally shape the work item: a summary template (tokens like {{environment}}, {{title}}), labels, and priority by Sentry level (for example fatal=Highest, error=High).
  8. If your issue type has required custom fields, add one line per field, such as customfield_10051={{environment}}.
  9. Click Save.

Step 5: Verify with a test work item

On the same project settings page, click Create a test work item. The app runs your saved configuration — issue type, priority rules, summary template, labels, and required custom fields — and creates one clearly marked, safe-to-delete work item. If a required field is misconfigured you see the exact Jira error here, not on your first real incident. The admin page also shows a six-step setup checklist, including whether a verified webhook has arrived from Sentry yet.

Already have unresolved errors in Sentry? Click Import unresolved Sentry issues to open work items for your existing backlog — about 25 per run, skipping issues that already have one. Progress is saved per Sentry project, so running it again continues where the last run stopped; the result line tells you when more remain. Environment and minimum-level filters apply to imports; the "only alert rules" mode does not — an import is an explicit decision to create.

Step 6 (optional): Use an alert rule instead of every new issue

New issues in mapped projects already create work items through the issue webhook. To create tickets only for some alerts (for example "more than 100 events in 1 hour"), set the project's create mode to Only Sentry alert rules, then:

  1. In Sentry, go to Alerts → Create Alert → Issues.
  2. Set your conditions, then under Then perform these actions pick Send a notification via an integration → Jira (Autoticket).

Step 7: Test live

Trigger a test error in a mapped Sentry project. A Jira work item should appear within about 30 seconds. Resolve it in Sentry, and the Jira work item should move to Done within seconds. Every step shows up in the Recent activity list on the settings pages.

Troubleshooting

  • No work item: check the Recent activity list on the settings pages — it shows every processed event, including filtered (with which filter and why) and unmapped (the Sentry project slug didn't match any enabled Jira project).
  • HTTP 403 creating work items: give the app's user Browse Projects, Create Issues, Edit Issues, Link Issues, Transition Issues and Add Comments permissions in the project's permission scheme.
  • Sentry shows webhook errors in Developer Settings → your integration → Dashboard: a slow first response after an idle period can time out on Sentry's side while the ticket is still created. If a ticket is actually missing, email support@integrationyard.com with the request id.
  • Ad blockers: no action needed — the settings pages are Atlassian-hosted Forge UI with no third-party scripts.

Support Product overview