Unable update custom field : Getting 'anycustomfiield 'to cannot be set. It is not on the appropriate screen, or unknown

Hello Team,
I am unable to create issue with custom field values. Everytime I try tha using frest API get “'anycustomfiield 'to cannot be set. It is not on the appropriate screen, or unknown.”

But able to create the issue manually.

{
    "issueUpdates": [
        {
            "updates": {},
            "fields": {
                "issuetype": {
                    "id": "10102"
                },
                "parent": {
                    "key": "SP"
                },
                "project": {
                    "id": "10215"
                },
                "**Profile Testing Required**": "Feature P"       
            }
        }
            ]
        }

I am using bulk issue create API for doing so.
Added this field to required screen but still getting same error. read all the existing solutions but none of them worked.

Response coming:

{
    "err": {
        "issues": [],
        "errors": [
            {
                "status": 400,
                "elementErrors": {
                    "errorMessages": [],
                    "errors": {
                        "Profile Testing Required": "Field 'Profile Testing Required' cannot be set. It is not on the appropriate screen, or unknown."
                    }
                },
                "failedElementNumber": 0
            }
        ]
    }
}

If a field is not configured to appear on the edit screen, then it will not be in the editmeta, and a field validation error will occur if it is submitted.

https://docs.atlassian.com/software/jira/docs/api/REST/8.5.0/#api/2/issue-editIssue

1 Like

Hi I am able to manually edit my custom field in a manually created task :

Using the Get Issue By Key Action I can locate my custom field value

},
  "customfield_12328": "THIS IS MY LOVELY GUID",
  "watches": {

But setting this in a Power Automate Create Task Action with the following json request body:

 },
    "customfield_12328": "a7a351c7-38ad-4f72-b4d3-e4e87988957b",

Will give you this nice error

{“errorMessages”:[],“errors”:{“customfield_12328”:“Field ‘customfield_12328’ cannot be set. It is not on the appropriate screen, or unknown.”}}

It is the correct name for the custom field so I am bit baffled

Hmmmmmm , just moved the field in the json to just under the the “fields {” and it works ok. As to why … :thinking:

{
  "fields": {
    "customfield_12328": @{guid()},

Please check this out.