Field 'summary' cannot be set - Create Issue API - JIRA Cloud

[Steven Lloyd]

I am currently struggling to get around an issue I am encountering when trying to create using the API on Postman, I am relatively new to this side but when I try to send I am receiving;

"reporter": "Field 'Summary' cannot be set. It is not on the appropriate screen, or unknown."

After having a look around I believe this is potentially an issue with the authentication and permissions to be able to create the issue rather than the summary not being on the appropriate screen as Summary is on both the create/edit/view screen of what I am trying to create.

Any assistance would be greatly appreciated

[Warren]

Hi @Steven Lloyd 

I would recommend doing a simple pull of data in Postman to know that your authentication is working before you try to set data. So try something like 

rest/api/2/issue/ABC-123

replace ABC-123 with a key that you know exists and you have access to.

If that works then you should be better placed to try a POST

[JIRA BSA]

Hi Warren,

Thank you for your response, 

If i understand correctly I used as the above with the replaced key from my JIRA and received;

{ "errorMessages": [ "Issue does not exist or you do not have permission to see it." ], "errors": {}}

[JIRA BSA]

Cheers for getting back Warren, it was an authentication error managed to sort it after sitting at the screen banging my head for several hours

[Shane J]

Steven can you share what you did to fix it?

[Michiel Spoor]

I had the same issue - turned out I had "api-name:api-token" in the authentication header, in stead of "email-address:api-token"... That solved the problem for me.

If the error had indicated an authentication error, it would have samed my a LOT of time :-)

[Animesh Soni]

GOT The Solution please apply this one ::-

See 1st of all for every account they have different issue id.... yesss its looks wrong but it what it is... so we please do 1 thing 1st check all params i.e email ,token, url are correct then., insert issue based on  'name' not id... or to check issue id for your accunt/project hit 

https://<your account>.atlassian.net/rest/api/3/issuetype

then write code accourdingly... 

[DPKJ]

@Steven LloydCan you please give full request and response sample, like error code and full json response.

Also try using 'summary' instead of 'Summary'.

[JIRA BSA]

Hi,

So I used;

{
"fields": {
"project":
{
"key": "JIR"
},
"summary": "testing.",
"description": "new",
"issuetype": {
"name": "Test"
}
}
}

And received the below

{ "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." }}

[DPKJ]

I tried same with curl on my instance and this worked I am adding curl code. Check if this works.

curl --request POST \
--url 'https://<SITE_URL>/rest/api/3/issue' \
--user '<EMAIL_ID>:<API_TOKEN>' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '{
  "fields": {
    "project": {
      "key": "<PROJECT_KEY>"
    },
    "summary": "Sample issue summary",
    "issuetype": {
      "name": "<ISSUE_TYPE_NAME>"
    },
    "description": {
      "type": "doc",
      "version": 1,
      "content": [
        {
          "type": "paragraph",
          "content": [
            {
              "text": "description",
              "type": "text"
            }
          ]
        }
      ]
    }
  }
}'

Please replace <SITE_URL>, <EMAIL_ID>, <API_TOKEN>, <PROJECT_KEY>, and <ISSUE_TYPE_NAME> with appropriate values.