One JIRA got auto raised by one internal process
The screen opened and suddenly displays the following
Something went wrong on our end
If this keeps happening, share this information with your admin, who should contact support.
Hash RZ617O Trace 9dcf9dc9297f49f4bb29eab001cd8c18Hello @Venkatesh E
That error with a Hash + Trace ID is a Jira Cloud backend error.
Since it happens only for you (others can open the same issue), it’s usually one of these:
Account/session issue (stale session, bad cookies)
Browser extension / network proxy interfering
Your user has something “special” on that issue (permissions edge case, broken mention/watch state is rare but happens)
Profile/account mismatch (logged into the wrong Atlassian account in the browser)
What I’d do (fast, in order):
Open the issue in an incognito/private window and log in fresh.
If that works, clear cookies for atlassian.net or just sign out/in.
Disable extensions (AdBlock, script blockers) and try again.
Try a different network (VPN off / mobile hotspot) to rule out proxy filtering.
If it still fails only for your user, ask your admin to open an Atlassian support ticket and include:
the issue key
timestamp/timezone
the Hash (RZ617O) and Trace (9dcf9dc9...)
That’s exactly what Atlassian needs to find it server-side.
I wish you a great Day.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.