Close the Jira ticket when the Sentry issue is resolved
Errors get fixed in code and resolved in Sentry, but the Jira ticket stays open (or the other way round). This guide covers ways to keep Sentry and Jira status in step.
Disclosure: Integration Yard makes Autoticket, one of the options below. Autoticket is pending Atlassian Marketplace approval as of October 22, 2026.
Sentry's own Jira integration
Sentry's Jira integration has status-sync settings that map Sentry resolve and unresolve to Jira statuses. Check Sentry's docs and pricing for what your plan includes. If tickets are linked and sync is configured there, you may not need anything else.
Webhooks you wire yourself
Sentry internal integrations send issue webhooks with resolved and unresolved
actions. A small service (or Jira Automation's incoming webhook trigger) can transition the linked Jira ticket.
The reverse direction needs a Jira webhook or Automation rule calling Sentry's issue API with
{"status": "resolved"}. Watch out for loops: each side's update fires the other's webhook.
Autoticket
- Resolving or archiving in Sentry moves the linked Jira work item to a Done-category status (or one you name) and adds a comment. If the workflow has no matching transition, it only comments.
- A regression in Sentry reopens the work item, if you leave reopen on.
- Moving the work item to Done in Jira resolves the Sentry issue; moving it out of Done unresolves it.
- It ignores the echo of its own changes, so the two sides don't loop.
It also creates the tickets in the first place, including on Sentry's Team plan. See the Team-plan guide and setup guide.
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.