Next-gen: Cannot create issue with a custom field through API.

[EP]

I'm sending a POST request to  /rest/api/2/issue endpoint.

I can create an issue without the custom field just fine but when I add the custom field it complains:

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

I've added this field using GUI in project settings. Please let me know how can I "add it to the appropriate screen".

Best & Happy New Year!

EP

[Nic Brough -Adaptavist- · Accepted solution]

It looks like you have literally copied "custom_field_name" into your code, rather than replacing it with the name of the custom field you are trying to set.

To check the Jira side of this, log in as the same person as is used in your script, click "create" and check the names of the fields that are shown to you.  The REST API respects what is set for interactive users.

[EP]

Thanks for your response. I used the correct field name ( I put custom_field_name here to make it easier to understand that I was referring to my custom field).

So when I login interactively I see the same name I use through my API (the real name is reporter_email) see image attached.

And the exact error I get is:

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

[EP]

EDIT: I posted my reply twice because Jira did not show it at first.

[Nic Brough -Adaptavist-]

Hmm.  Could you try replacing your field name with the customfield id?  I.e.   "customfield_12345"?

[EP]

Thanks, this really helped. Now it works.

(I found the id by inspecting the element when I was editing the form).

[Warren]

Hi @EP 

That field needs to appear on the equivalent of one of the Edit screens in the "old UI view" - if it isn't there, you won't be able to set the field value through the API

[EP]

How do I access the "old UI view"?

[EP]

PS. I'm on a next-gen project.

[Warren]

Hi @EP 

Sorry I missed the Next Gen part - I don't think my comment is appropriate then, please ignore