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!


A user is getting the following error when attempting to create an issue through the API: 

00 Bad Request
"errorMessages": [
"Unrecognized field \"fields\" (Class, not marked as ignorable\n at [Source: org.apache.catalina.connector.CoyoteInputStream@98f8994; line: 2, column: 16] (through reference chain:[\"fields\"])"

This is the JSON that is being sent via API, scrubbed of some information:


    "fields": {



          "key": "CT"


       "summary": "TEST",

       "description": "Test: Post Man REST API",

       "issuetype": {

          "name": "Opt In"


       "labels": ["LabelName"]




I would initially have assumed that the "fields" portion of the JSON is not properly configured. However, this same request works correctly in our QA environment. I have already confirmed that there are no conditions or required fields that would be preventing ticket creation, and that the user/password they are using has Jira access and has access to create tickets in the target project. Any assistance in decoding this error message would be appreciated. Please let me know if there is any other information I can provide.

1 answer

Are you on Server or Data Center? What is your Jira version?

We are on Data Center version 8.20.10 in both the QA and production environments.

@Adam van der Voorn _TechTime_

I'm still not able to find any cause for this error. Can you make sense of the error considering the same method is working in the QA environment?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events