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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

OpsG to JSM issue

Hi there, I have JSM > OpsG working fine.  For some reason, If I trigger an alert on OpsG, I get an email and SMS, but it fails to create a ticket on JSM.

In the OpsG log, I can see the following Error

  • alertLogOwner System

  • responseBody {"errorMessages":[],"errors":{"summary":"Field 'summary' cannot be set. It is not on the appropriate screen, or unknown.","description":"Field 'description' cannot be set. It is not on the appropriate screen, or unknown.","labels":"Field 'labels' cannot be set. It is not on the appropriate screen, or unknown."}}

  • _outgoingData

    • _headers

      • Authorization ...

      • -Content-Type [ application/json;charset=UTF-8 ]

    • integrationType JiraServiceDesk

    • _payload

      • _fields { summary: testing 20202020, -labels: fromOG, _project: [object Object], _issuetype: [object Object], description: Click on [Body.html] attachment for HTML version Testing 123  }

    • integrationName VoIP_Jira Service Management

  • alertId d42eaa38-d2f1-45fa-ba3d-2ba5b1081d3a-1606840532978

  • alertLogType system

  • statusCode BAD_REQUEST
    I take it I am missing an setting somewhere?



2 answers

1 accepted

2 votes
Answer accepted
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 01, 2020

Hi @Mick Love ,

There are a few things to review for this error.

In JSM navigate to the Settings menu >> Issues tab >> Screens tab >> click Configure for the same project’s screen that is configured in the integration’s action mapping section, and check if these fields - summary, description, and labels - are available in this screen:

JSM comm 1.jpgJSM comm 2.jpg


Typically when we see this error including all 3 fields missing, the fields are found in the project's Screen - and instead, it could potentially be a misconfiguration here in the integration:

JSM comm 3.jpg


A few things to double-check on your end:

  1. If OEC is not being used - make sure the 'Send Via OEC' checkbox is not selected. OEC is used mostly for Server instances - and typically not needed with Cloud instances:
  2. URL should only include your site name with nothing following .net
    1. Example:
  3. Username is the email used to log in into your Atlassian site. Best practice is using a site admin's email.
  4. Password/API Token - best practice is using an API token here. This doc outlines how to generate one:
    1. After you create / copy the API token, paste it into the Password/API Token field.

Finally - save the integration, and retest.

Let us know if you continue seeing this 400 error after.

@Nick H thank you for the very detailed help, it ended up being my credentials. I was using my Displayed username and not my email. 

All working now :)




Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events