All workflows
Open a Jira bug for every fatal Sentry error
When Sentry reports a new fatal error, creates a Highest-priority Jira bug and posts both links in Slack.
On new issue in Sentry3 apps3 steps
What it does
Each integration step this workflow runs, in order, what it is for, and the conditions and loops that decide when it runs.
- 1SentryNew issue triggerStarts for each new fatal error in your project.
- 2JiraCreate issueOpens the bug.
- 3SlackSend messagePosts the Jira and Sentry links.
How it works
What happens on each run, in plain English.
A fatal error should never wait for someone to notice it. When Sentry opens a new fatal error in your project, this creates a Highest-priority bug in Jira saying where it happened and how many times, with the Sentry link.
The team is told in Slack with links to both, so the bug has an owner-in-waiting within moments.
sentryjiraslackbugs
You may also be interested in
Monday list of unassigned bugs older than 30 daysPosts the bugs that nobody has picked up in a month to Slack every Monday.
Alert on-call about new top-priority Jira bugsWhen a Jira bug is created with the highest priority, posts in Slack and emails the person on call.
Daily Jira status report to SlackCounts your Jira tickets by status every morning and posts the breakdown to Slack, with a short read on what stands out.
Turn new GitHub bugs into Linear issuesWhen the bug label is added to a GitHub issue, creates a matching Linear issue and tells your team in Slack.Start from a workflow that already works.
Add "Open a Jira bug for every fatal Sentry error" to your workspace, connect its apps, and make it yours.
Free plan, no credit card