I've started a brand new jira instance, it is clean.
I created a new sample project (with fake data) and added a new text field "myt". I associated it with all projects, and with all screens.
I can create an issue from the UI, and that new field appears.
However when I try to do the same from the API, it fails with
{"errorMessages":[],"errors":{"myt":"Field 'myt' cannot be set. It is not on the appropriate screen, or unknown."}}
Creating a issue from the API without that field works fine.
I've read this problem could be related to a screen association issue, but I already added my field to all screens, so I don't think it's that.
What else could be the issue ?
Thanks
Hi @wikabi9119 ,
custom fields in REST api need to be referenced through id and not using the name. "myt" should be something like "customfield_XXXXXX".
Hope this helps,
Fabio
Hi @wikabi9119 ,
I know that you checked that the field appears in the screens, but just in case, did you verify that it's in all types of screens (more specifically the 'create' one? Also, check this out: https://community.atlassian.com/t5/Adaptavist-questions/Field-customfield-10011-cannot-be-set-It-is-not-on-the/qaq-p/1672153
When you create the issue manually, can you set the field 'myt'? Is it possible that there is more than one field called 'myt'?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I figured it out, it needs to be set by its custom field id, not name
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.