Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Could not send [createIssue] action to JiraServiceDesk, error 400

I've been trying to create an integration between Opsgenie and Jira Service management, that whenever we receive an alert from our monitoring system in Opsgenie (which is currently working, Zabbix 6.0.13) a ticket is created with that information in Jira Service management. 

I've followed the documentation (keeping in mind NOT to check OEC), using the right project Key, API token for an user with enough permissions, etc. 

I'm getting the following:

[system] Could not send [createIssue] action to JiraServiceDesk [Zabbix to JIRA]. Reason: 400 Bad Request: "{"errorMessages":[],"errors":{"labels":"Field 'labels' cannot be set. It is not on the appropriate screen, or unknown."}}"

"alertLogOwner": "System",
"responseBody": "{\"errorMessages\":[],\"errors\":{\"labels\":\"Field 'labels' cannot be set. It is not on the appropriate screen, or unknown.\"}}",
"_outgoingData": {
"_headers": {
"-Content-Type": [
"-Authorization": ........
"integrationType": "JiraServiceDesk",
"_payload": {
"_fields": {
"summary": "[Zabbix] Alert from Zabbix",
"-labels": [
"_project": {
"key": "IT"
"_issuetype": {
"name": "Incident"
"description": "The alert has no description."
"integrationName": "Zabbix to JIRA"
"alertId": "7277dde3-48a4-4d86-bb50-0d514e12ef48-1678750074990",
"alertLogType": "system",
"statusCode": "BAD_REQUEST"

Would appreciate any help you guys can provide. 

1 answer

1 accepted

0 votes
Answer accepted
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 14, 2023

Hi @Andrés Enrique Cárdenas ,

You should be able to correct this in JSM by navigating to the Settings menu → Issues tab → Screens tab → Configure the same project’s screen that is configured in the integration’s action mapping section:



Add any fields to this Screen that appear in 400 error (labels, summary, description, etc.):



If the Labels field exists under this screen, another way to check within JSM is by creating an issue under the project in question, and selecting the Find your field option:



If you search for the Label field (or any in general), there should be an error if the field does not exist in the project / issue. You should also then be able to click into Screen where it needs to be added:


thank you, that was pretty easy to follow and solve, tickets are now being created in JIRA. 

Like Nick H likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events