Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

ERROR: CJ8G6B - Copied link cannot open in another client

Hi all,

I am developing plugins for jira cloud. When I try to share a link to another, the other client cannot open that link with query string. It gets an error "Something's gone wrong Our team has been notified. If the problem persists, please contact Atlassian Support. ERROR: CJ8G6B Reload page". 

https://mesutcan.atlassian.net/plugins/servlet/ac/com.obss.plugin.time-in-status/time-in-status?parameterSet=97c20ec6-d43f-4e1b-894e-d16d1c47549f 

What is the reason of that? Thank you for your time.

1 answer

0 votes

That code doesn't really tell us, the end user, anything.  It's actually a tag for Atlassian to say "this error has occurred for this set of Cloud systems (it could be just your system, it could have happend on others too)".  It's a bit more clever than just "look for this code in the logs ", but that's essentially all it is - a tag for collecting information about the problem from all the various places you might want to look in the back end.

For us, it just enables Atlassian to quickly locate what went wrong, and potentially tell you what they're doing about it, or what has been fixed and possible outcomes, without having to go and ask the support people for all the potentially affected clients who ask about it.

So, while the error message tells us nothing, there are two things you can do - first, retry, as Atlassian may have fixed it by now.  Second, report it to Atlassian as a support call and see what they say.

@Nic Brough _Adaptavist_ thank you for your response, actually I was expecting Jira to redirect to login page if the user is not logged in, but it gets 401 error and not redirecting.

That does not seem to have anything to do with what you asked about earlier.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

109 views 7 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you