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

Luca Stanger February 13, 2020

Hi,

 

i've created an application to duplicate projects. Unfortunately I am not able to create Issues since i've swapped from our test environment to our productive one. It worked fine while using the test system. Our IT ensured me there's no difference in Jira version between these two systems.

 

I am creating my JSON as following:

tIssue := '{
"fields": {
"project":
{
"id": "|projectID|"
},
"summary": "|issue_.fields.summary|",
"description": "|issue_.fields.description|",
"issuetype": {
"name": "|issue_.fields.issuetype.name|"
},
"priority": {
"name": "|issue_.fields.priority.name|"
},
"labels": [|tLabels|]
}
}';

 

The error i am generating from the REST-API is shown 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.","priority":"Field 'priority' 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."}}

 

How to fix this?

 

I would be very thankful for a reply!

5 answers

2 votes
Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 13, 2020

Hi Luca,

did you check for permissions? I came across a few cases where the user (=the user which you are accessing the API with) is missing a membership in the appropriate role or group.

From what I observed in all cases (even it is not a specific permission problem here) that the non-production environment and the production environment differs in one or more little aspects - a thorough comparison of borh systems should help sorting the current issues out.

Cheers,
Daniel

mohamed gamal September 20, 2021

@Daniel Ebers how to check permissions? i can create any issue in jira website 

Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 26, 2022

For a first diagnosis I would go with "Permission Helper" from "Admin Helpers" - just to rule out the account in question is lacking permissions:

https://confluence.atlassian.com/adminjiraserver/jira-admin-helper-938847791.html

Austin Johnson September 8, 2022

I was trying to use a service account via the API and this was exactly my issue. 

I needed to add the service account to the projects IN JIRA and then it had no issues making the changes via the API 

thank you @Daniel Ebers 

1 vote
mohamed gamal September 20, 2021

the same issue here can any one help

0 votes
AMAN DIXIT
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 9, 2024

The issue in my case was I was not passing JSESSIONID properly in header. And yes API error response message is confusing.

0 votes
DH November 10, 2021

Jira Data Center has same issue.  I try to create an issue using curl:

 

Command

curl -H "Authorization: Bearer <insert token>" -d @[deleted]_payloadsmall.json -X POST -H "Content-Type: application/json" -H "Accept: application/json" "https://<server>/rest/api/2/issue"

 

Payload is:

{

    "fields": {

        "project": { "key": "PTEST" },

        "summary": "IGNORE - Created for testing",

        "issuetype": { "name": "Bug" }

    }

}

 

Response

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

 

This message is bogus because the summary field exists on the create screen.

  • If I use my own personal bearer token, this works.
  • If I use the bearer token of the service account, this fails. 

So in my case,

  • it is not a project permission issue.
  • it is not an issue with a field missing from the screen.
  • it is an issue with the user account.

Every company has their own authentication and authorization. We use One Login. And for that, I found out that our user/service accounts must have a particular header 'X-Auth-Params-Email' to be configured.

In our case, when that is missing, Jira receives the api call but is missing that header in the request so it thinks it is coming from an unauthorized user. Thus, it is returning the error message.

 

...I am still waiting for our team to set that header to confirm this works, but if all else fails, look at the user account.

Mark Gingoyon December 7, 2021

Did this solve the issue, if so can you provide an example of what that header looks like? Thank you

Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 26, 2022

From last experience it is very true that an authentication problem can cause the message even if the field is present on the screen.
Also, like added to the last comment here, missing permissions (even when authentication is fine) can lead to the error message which can be a bit confusing, yes.

There is a bug open with Atlassian which describes it even better:

0 votes
Andrew Morin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 13, 2020

Is the Summary field on your Create screen?

Suggest an answer

Log in or Sign up to answer