Getting 400 from Jira while trying to create an alert from Opsgenie

Awais Ali March 3, 2020

Hey, I have configured the JIRA and Opsgenie integration. But when it tries to create an issue it returns a 400 from JIRA, any ideas?

Could not send [createIssue] action to JiraServiceDesk [JiraServiceDesk - DevOps]. Reason: 400

 

{
"alertLogOwner": "System",
"responseBody": "{\"errorMessages\":[],\"errors\":{\"issuetype\":\"issue type is required\"}}",
"_outgoingData": {
"_headers": {
"Authorization": "...",
"-Content-Type": [
"application/json;charset=UTF-8"
]
},
"integrationType": "JiraServiceDesk",
"_payload": {
"_fields": {
"summary": "Test Alert from Opsgenie",
"-labels": [
"fromOG"
],
"_project": {
"key": "DEVOPS"
},
"_issuetype": {
"name": "Task"
},
"description": "The alert has no description."
}
},
"integrationName": "JiraServiceDesk - DevOps"
},
"alertId": "4gh3bsfk9-88b3-555n-9b97-23432b234234-234234234234",
"alertLogType": "system",
"statusCode": "BAD_REQUEST"
}

I have double-checked the configurations and they are set up correctly though.

Screen Shot 2020-03-03 at 4.17.31 PM.png

 

 

Screen Shot 2020-03-03 at 4.19.15 PM.png

3 answers

1 accepted

0 votes
Answer accepted
Awais Ali March 4, 2020

I have resolved this by creating a new issue type in Jira with the same name that I am providing in the Issue Type Name field.

1 vote
Samir
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 4, 2020

Hi @Awais Ali  - it looks like it's saying there is no issue-type specified. In your Jira integration in Opsgenie, did you specify the issue-type you want the Jira issue to be created with in this field?

jiraScreen.png

Awais Ali March 4, 2020

Hey @Samir,

Thanks for the reply. I am providing the issue type. I have resolved this by creating a new issue type in Jira with the same name that I am providing in the Issue Type Name field. 

The opsgenie integration marks the fields shared in the screenshot as mandatory so you have to provide these in order to set the integration up (if you have not checked the oec checkbox)

I was supplying the same issue types that I had in my project in Jira previously as well but I guess there was some access issue that was not causing it to create the issues on Jira. This was all set once I created a new type with no restrictions. Anyways this is good to close now. 

Like Samir likes this
0 votes
GlennF April 8, 2020

@Awais Ali how were you able to get the response JSON from the request?  I am seeing similar issues but intermittently.  I suspect there are ascii characters in my requests but I can't figure it out since I can't figure out how to get the response JSON.

 

Thanks in advance!

Awais Ali April 8, 2020

Hey, @GlennF  I got this from Opsgenie. If you navigate to

yourapp.opsgenie.com/settings/log

you will see warn and error level logs. From there you can see what is the response JSON sent from Jira.

You can search on the basis of the alert for which it's causing issues. 

 

Let me know if that is what you want or is there anything else you are looking for

GlennF April 9, 2020

Brilliant!  Thanks @Awais Ali ~

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events