Hi!Today, we encountered a problem: We cannot create a Jira issue from Sentry; we get a 504 (timeout) error.At the same time, there are no problems in creating a Jira issue directly in Jira UI.Is everything ok on the Jira side?
Hey @nladygin
Welcome to Atlassian Comunity!
There are no incidents reported today that might be causing this. Interestingly, I also didn't find anything reported on Sentry's site: https://status.sentry.io/
You may check their support info here for further assistance: https://marketplace.atlassian.com/apps/1219432/sentry-for-jira?tab=support&hosting=cloud
Thanks!
For anyone landing here from search with the same 504: that timeout is Sentry'scall into the Jira REST API failing, which is why creating the issue directly inthe Jira UI still works fine. Things worth checking in that order:
- Whether your Jira site has an IP allowlist or firewall rule that Sentry'soutbound calls don't satisfy- Whether the Jira project has required custom fields — Sentry's create-issueform doesn't always surface them, and the call hangs or fails- Whether the account behind the integration still has Create Issues permissionin that specific project- Ad blockers and corporate proxies during setup, which break the config screenrather than the API call itself
Disclosure: this problem annoyed me enough that I built an alternative, so treatthe rest as biased. Sentry Bridge for Jira is a Forge app, which means the Jiracall happens inside Atlassian rather than as an inbound call from Sentry'snetwork — so this class of timeout doesn't arise. It works off the `issue`webhook that every Sentry plan can send, dedupes, and reopens the ticket when aclosed error comes back.
https://marketplace.atlassian.com/apps/3885567652/sentry-bridge-for-jira
Either way, hope the checklist helps.
It looks like you're new here. Sign in or register to get started.
