Cann't create or link to Jira tickets

Yui

Posted on
Mar 30 2016

Hi there,

I wasn't able to create a new Jira ticket or link tickets to existing errors in Raygun. It said "Something went wrong, Here is what your Jira server returned: Internal Server Error" when I created a new ticket and "Could not get issue from Jira, please check your provide setting" when I tried to link an error with a ticket. Also, we haven't touched or upgrade our Jira server. Can you please check what cause of issue?

Thanks Yui


Daniel

Posted on
Apr 04 2016

Hey Yui,

Are you still experiencing issues? I have just had a quick look your applications and they appear to be loading data from your JIRA instance now?

Regards, Daniel


Yui

Posted on
Apr 04 2016

Hi Daniel,

It's all good now.

Thank you :D


Daniel

Posted on
Apr 04 2016

Awesome, glad to hear!

Daniel


rmccord

Posted on
Oct 15 2016

hi Daniel

I couldn't find any other threads that pertained to this issue, but we're running into the same "Something went wrong! Here is what your Jira server returned: service returned: Internal Server Error"

We're getting this when trying to create an issue from the crash reporting page. We had no issues initially setting up the integration to our JIRA which is via reverse-proxy (nginx).

This is the message we're getting back that I picked up on the proxy ...

54.227.14.254 - raygun.errors [14/Oct/2016:16:49:34 +0000] "GET /rest/api/latest/issue/createmeta?expand=projects.issuetypes.fields HTTP/1.1" - 200 33039229 "-" "RestSharp/105.2.3.0" "-"

Deleted User

Raygun

Posted on
Oct 26 2016

Hi Rick,

I believe you have an answer to this already but thought I'd post it here for the benefit of others.

This issue can arise when a JIRA instance has required fields that we don't cater for in our UI, for example Components. Unfortunately we don't provide a way to set other required fields within the app at the moment.

We are going to see if we can improve our support for non-default required fields in the near future. For the time being removing the requirement for the field should enable our API call to succeed.


Reply