Two-way status sync
Autoticket keeps Sentry issue status and the linked Jira work item in sync in both directions. Creation filters (environment allowlist, minimum level, alerts-only mode) apply only when opening a new work item. Once a ticket exists, comments and status updates still flow.
Sentry → Jira
When a mapped Sentry issue is resolved, archived, or marked ignored, Autoticket looks up the linked Jira work item and tries to move it to a Done-category status (or a name you set in Resolved status names). When the issue is regressed or unresolved and reopen is left on (the default), Autoticket tries to move that same work item out of Done, using Reopen status name if you set one, or the first available To Do or In Progress transition if you left it blank, and adds a comment. If reopen is turned off, Autoticket comments on the existing work item instead of reopening it.
If the workflow has no matching transition, Autoticket leaves the Jira status unchanged and adds a comment explaining that no matching transition was found.
Jira → Sentry
Moving a linked Jira work item to a Done-category status (or a name in
Resolved status names) resolves the Sentry issue. Moving it out of Done unresolves the
Sentry issue. The activity log records these as resolved-sentry or
unresolved-sentry.
This path needs a real Sentry issue id on the work item. A metric-alert-only ticket, or the synthetic Create a test work item ticket, has no Sentry issue to update: Autoticket comments to say so rather than guessing. Use a real linked pair to test reverse sync, as described in the evaluation guide.
If the Sentry update fails after retries are exhausted, Autoticket comments once on the Jira work item with the error.
Loop protection
Autoticket records the change it just made and ignores the matching echo from the other side, so resolving in Sentry does not bounce back as a second Jira-to-Sentry resolve, and the other direction is protected the same way. The Jira trigger also ignores events the app generated itself.
The sentry_bridge property on sync
Status sync in both directions refreshes the versioned sentry_bridge issue property
(at least its status field) and keeps the agent fields that were written at create time,
such as environment, release, frames, and agentReady. It does not rewrite the description
of an already-created ticket. See
Using Autoticket with agents.
Settings that affect sync
- Reopen the work item when Sentry marks the issue regressed or unresolved — on by default, on the project settings page.
- Resolved status names and Reopen status name — optional; see configuration.
Compared with Sentry's own Jira integration
Per Sentry's Jira integration docs, issue sync (including status, both directions) and manual ticket creation are available on the Team, Business and Enterprise plans, while automatic ticket creation is Business and Enterprise only. If your tickets are linked and Sentry's sync is configured, you may not need anything else.
Autoticket also creates the tickets in the first place, including on Sentry's Team plan. On top of status sync it handles archived and ignored issues, named resolved and reopen statuses, a comment when no transition matches, loop protection, and reopening regressed tickets with a comment. Other options are compared in Close the Jira ticket when a Sentry issue is resolved and the Team-plan guide.
FAQ
Does Autoticket sync Sentry and Jira status in both directions?
Yes. Autoticket keeps Sentry issue status and the linked Jira work item in sync in both directions.
What happens when I resolve or archive a Sentry issue?
When a mapped Sentry issue is resolved, archived, or marked ignored, Autoticket looks up the linked Jira work item and tries to move it to a Done-category status (or a name you set in Resolved status names).
What happens when I move the Jira work item to Done?
Moving a linked Jira work item to a Done-category status (or a name in Resolved status names) resolves the Sentry issue. Moving it out of Done unresolves the Sentry issue.
Does a Sentry regression reopen the Jira ticket?
Yes, if reopen is left on (the default): Autoticket tries to move that same work item out of Done and adds a comment. If reopen is turned off, Autoticket comments on the existing work item instead of reopening it.
What if the Jira workflow has no matching transition?
Autoticket leaves the Jira status unchanged and adds a comment explaining that no matching transition was found.
Will updates loop between Sentry and Jira?
No. Autoticket records the change it just made and ignores the matching echo from the other side. The Jira trigger also ignores events the app generated itself.
Do creation filters also apply to status sync?
No. Creation filters (environment allowlist, minimum level, alerts-only mode) apply only when opening a new work item. Once a ticket exists, comments and status updates still flow.