Frequently asked questions
Answers pulled straight from how Autoticket actually works — no spin.
Questions and answers
Does it work on the Sentry Team plan?
Yes. Autoticket is built specifically to add automatic ticket creation for Sentry plans — like Team — where Sentry's own integration requires a manual click for every issue.
Is self-hosted Sentry supported?
Not in v1. Autoticket supports sentry.io (US) and regional SaaS hosts such as de.sentry.io. Self-hosted Sentry isn't supported yet.
How fast is the sync?
New Sentry issues usually appear in Jira within about 20–30 seconds, mostly Sentry's own processing time. Sentry → Jira status changes sync within seconds. Jira → Sentry changes usually take about 1–2 minutes, because Atlassian batches Jira event delivery.
What does the app have access to?
Only Sentry. The app's only outside network call is to sentry.io and *.sentry.io. The optional AI summary never leaves Atlassian's own infrastructure, and there's no other external service.
Will I get duplicate tickets?
No. Each Sentry issue maps to exactly one Jira work item, or one per environment if you choose that deduplication rule.
Can I keep staging noise out of Jira?
Yes. Each Jira project can set an environment allowlist (for example only production), a minimum Sentry level, or switch to "only alert rules" mode so your Sentry alert conditions — like "more than 100 events in an hour" — decide what becomes a ticket. Filtered events show up in the activity log with the reason, so nothing is silently dropped.
Can I import errors that happened before I installed?
Yes. The "Import unresolved Sentry issues" button fetches your currently-unresolved Sentry backlog and opens work items for the ones that don't have one yet, about 25 per run in dedupe-safe batches. Pagination progress is saved, so running it again continues where the last run stopped, and the result line tells you when you've reached the end.
How do I know the sync is actually working?
Two ways. The settings pages show a live activity log of the last 50 events — created, synced, filtered (with the reason), and errors. And a "Create a test work item" button runs your exact configuration — issue type, priority rules, templates, required fields — and creates one clearly marked, safe-to-delete work item so you can verify the result before the first real error.
Who can configure the app?
Connecting Sentry is limited to Jira admins. Mapping individual Jira projects is limited to project admins.
Is the AI summary required?
No. It's off by default. When a Jira admin turns it on, Atlassian-hosted Forge LLMs generate a short summary, likely cause and suggested code area — no third-party AI key or extra egress involved.
How is this different from Sentry's own Jira integration?
Three things. Sentry's integration creates tickets automatically only on the Business and Enterprise plans — Autoticket does it on the Team plan too. Sentry's integration can't fill required custom fields on any plan — Autoticket fills them from templates. And when an error regresses, Autoticket reopens the existing ticket with a comment instead of leaving it closed. Full comparison of your options, or Autoticket vs. Sentry Business pricing.
Does setup work with an ad blocker on?
Yes. The admin and project settings pages are Atlassian-hosted Forge UI with no third-party browser scripts, so ad blockers and strict corporate proxies have nothing to block.
Will the Sentry panel show up in every project?
No. The panel appears only on work items that are actually linked to a Sentry issue — it stays out of the way everywhere else.