Quietstack

Sentry Bridge for Jira — setup & support

Set up in under five minutes

1. In Jira

Open the project you want errors filed in → Project settings → Apps → Sentry Bridge.

Turn Enabled on.
Issue type — the app pre-selects a Bug-like type, or a Task if your project has no Bug.
Minimum level — error is a sensible default; warning if you want more.
Environments — comma separated, e.g. production, staging. Leave empty for all.
Shared secret — any random string. Recommended: it stops anyone who guesses your webhook URL from filing issues in your project.
Press Save, then copy the Webhook URL at the bottom. It already contains your project key and secret.

2. In Sentry

Settings → Developer Settings → Custom Integrations → Create New Integration → Internal Integration.

Name: anything, e.g. Sentry Bridge for Jira
Webhook URL: paste the URL from step 1
Permissions → Issue & Event: set to Read
Webhooks → Issues: tick Created and Resolved
Save Changes

3. Prove it works

Back in Jira, press Send test event. You should see “Works. Created PROJ-123”. Open that issue, look at it, delete it. You are done.

How it behaves

Situation	What happens
New error in Sentry	A Jira issue is created with culprit, level, environment, event count, first-seen time and a link to Sentry (plus the stack trace, if your plan allows the `error` webhook — see Limits)
Same error fires again, issue still open	A comment is added with the current event count
Same error fires again, issue was closed	The issue is reopened into your chosen status and a regression comment is added
Error resolved in Sentry	The Jira issue moves to your chosen status (if you set one)
Error below your minimum level, or in an environment you didn’t list	Ignored

Settings reference

Move issue to this status when resolved in Sentry — type the status name exactly as it appears on your board. The settings screen lists your project’s statuses under the field. Leave empty to do nothing.
Reopen closed issues on regression + Status to reopen into — what to do when a closed issue’s error comes back.
Comment when the error recurs — comment on an open issue instead of staying silent.
Map Sentry level to Jira priority — fatal → Highest, error → High, warning → Medium. If your project doesn’t have those priority names, the app creates the issue without a priority rather than failing.

Troubleshooting

Nothing arrives in Jira.

Is Enabled on and did you press Save?
Press Send test event. If that works, Jira is fine and the problem is on the Sentry side.
In Sentry, is the webhook URL exactly the one from the settings screen, including the ?project= and &secret= parts?
In Sentry, is Issue & Event permission set to Read and is Issues → Created ticked?
Is your error above the Minimum level, and is its environment in your Environments list?

“Send test event” says the bridge replied 401.

The secret in the webhook URL doesn’t match the one saved in settings. Press Save, then copy the webhook URL again — it’s regenerated with the current secret.

Issues are created but the status never changes when I resolve in Sentry.

The status name must match exactly. Check the list of statuses printed under the field. Also make sure Issues → Resolved is ticked in your Sentry webhook settings.

Duplicate issues.

Shouldn’t happen — one Sentry issue maps to one Jira issue for the life of the installation. If you see duplicates, the two errors are different Sentry issues; Sentry decides grouping, not us.

Limits

Stack traces depend on your Sentry plan. Sentry’s issue.created webhook — the one every plan can use — carries the culprit, level, environment, event count and permalink, but not the exception or stack frames. If your plan lets you subscribe to the Errors → Created webhook resource, the app also puts the exception type, message and top stack frames into the issue. Either way the “Open in Sentry” link takes you straight to the full trace.
One Jira project per webhook URL. Want several Sentry projects in different Jira projects? Configure the app in each Jira project and use each one’s own webhook URL in the matching Sentry integration.
The app does not write back to Sentry (it has no network egress at all). Resolving a Jira issue does not resolve the Sentry issue.

Support

Email support@quietstack.app. Include your Jira site URL and the issue key or time of the problem — it makes diagnosis much faster.