Integration Yard
Contact support
ProductDocsSecuritySupportAbout Contact support

Evaluation guide

This page is for Atlassian Marketplace reviewers and anyone evaluating Autoticket on their own Jira Cloud site and Sentry organization. It mirrors the setup guide with a shorter path focused on verifying create, sync, the Jira-side test button, and agent pickup.

Prerequisites

  • A Jira Cloud site where you can install apps (Jira admin).
  • A sentry.io organization on the Team, Business, or Enterprise plan with permission to create an Internal Integration (Owner or Manager). Sentry's free Developer plan cannot create the integration this app needs. Self-hosted Sentry is not supported.

1. Install Autoticket

Install Autoticket for Sentry and Jira from the Atlassian Marketplace listing with a Jira admin account. Then open Jira settings (⚙) → Apps → Autoticket and copy the Webhook URL (unique per site — treat it like a secret).

2. Connect Sentry

  1. In Sentry: Settings → Developer Settings → Custom Integrations → Create New Integration → Internal Integration.
  2. Paste the webhook URL. Enable Alert Rule Action.
  3. Permissions: Organization Read; Project Read (backlog import); Issue & Event Read & Write; everything else No Access.
  4. Enable the issue webhook (created, resolved, archived, unresolved).
  5. Save, copy the Client Secret, and create/copy an auth token.
  6. Back in Jira admin Autoticket: enter organization slug, base URL (https://sentry.io or a *.sentry.io regional host), client secret, and auth token. Save, then Test Sentry connection.

3. Map a project and use Create a test work item

On Project settings → Autoticket, enable creation, enter the Sentry project slug(s), choose issue type (and optional priority/templates), and Save.

Click Create a test work item. This runs your saved Jira-side configuration (issue type, templates, required custom fields) and creates one clearly marked, safe-to-delete work item without needing a live Sentry webhook. Use it to confirm mapping and field templates before relying on production errors. The test work item is not linked to a Sentry issue, so it does not get a sentry_bridge property, the Sentry panel, two-way status sync, or the agent-ready pickup label — use a real Sentry issue for those checks.

4. Trigger a real Sentry issue

Cause a test error in a mapped Sentry project (or fire an alert rule if the project is in "only alert rules" mode). Within about 30 seconds a Jira work item should appear. Check Recent activity on the settings pages for created / filtered / error outcomes.

  1. Sentry → Jira: resolve the real test issue in Sentry. Its linked Jira work item should move to a Done-category status (or your configured done status), provided that workflow transition is available.
  2. Jira → Sentry: trigger a different, new Sentry issue and wait for its linked Jira work item. Confirm this second Sentry issue is unresolved and the second Jira work item is not Done. Use this real linked pair, not the synthetic test-button item or a metric-alert-only item.
  3. Move that second Jira work item to a Done-category status (or your configured done status). Allow about 1–2 minutes for reverse sync, then verify that Sentry shows it as resolved and Recent activity shows resolved-sentry. If it fails, check the logged outcome and troubleshooting guide. Loop protection prevents the app's own status changes from ping-ponging.

5. Check the Agent brief and pickup label

On a real Sentry-sourced work item from step 4 (not the test-button item):

  • The description should start with an Agent brief section, ahead of the Sentry details. Fields the app does not have are labeled "not provided" rather than guessed.
  • The work item should have a sentry_bridge issue property (schema: 1), readable with Jira's getJiraEntityProperty tool. Status sync later refreshes this property; it does not rewrite the description of an already-created ticket.
  • The agent-ready pickup label (the default name; configurable per project) is added only when the event has at least one in-app stack frame, a non-empty release, and a Sentry level at or above the project's agent-ready minimum (error by default). An event with no recognized level never qualifies. If your test error was library-only, had no release, or was below that minimum, the ticket is still created — it just won't get the label.

Field-by-field detail: Using Autoticket with agents.

What to expect

  • Dedupe: one work item per Sentry issue by default (or one per issue and environment).
  • Activity log: rolling site-wide buffer of the last 50 processed events, including filtered events with reasons.
  • Two-way sync: Sentry → Jira on webhooks; Jira → Sentry on issue status transitions. See the two-way status sync guide.
  • Optional AI: off by default; when enabled, summaries use Forge LLMs inside Atlassian.

More detail: Configuration, Using Autoticket with agents, Troubleshooting, FAQ.

Setup guide Two-way status sync Using Autoticket with agents