Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot create a Jira issue from the Sentry

nladygin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 19, 2025

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?

2 answers

1 accepted

0 votes
Answer accepted
Karan Sachdev
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 19, 2025

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!

0 votes
Владимир
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 11, 2026

For anyone landing here from search with the same 504: that timeout is Sentry's
call into the Jira REST API failing, which is why creating the issue directly in
the Jira UI still works fine. Things worth checking in that order:

- Whether your Jira site has an IP allowlist or firewall rule that Sentry's
outbound calls don't satisfy
- Whether the Jira project has required custom fields — Sentry's create-issue
form doesn't always surface them, and the call hangs or fails
- Whether the account behind the integration still has Create Issues permission
in that specific project
- Ad blockers and corporate proxies during setup, which break the config screen
rather than the API call itself

Disclosure: this problem annoyed me enough that I built an alternative, so treat
the rest as biased. Sentry Bridge for Jira is a Forge app, which means the Jira
call happens inside Atlassian rather than as an inbound call from Sentry's
network — 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 a
closed error comes back.

https://marketplace.atlassian.com/apps/3885567652/sentry-bridge-for-jira

Either way, hope the checklist helps.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events