Missing custom fields via REST API

[Sandor Kocsis]

Hi everyone,

I'm trying to read custom fields ID -s via REST API, but it seems that certain custom fields that are shared between projects are not shown in the output of both.

Project-A:

https://emarsys.jira.com/rest/api/2/issue/createmeta?projectKeys=A&expand=projects.issuetypes.fields

"customfield_12850": { "required": false, "schema": { "type": "string", "custom": "com.atlassian.jira.plugin.system.customfieldtypes:textfield", "customId": 12850 }, "name": "Job Title", "key": "customfield_12850", "hasDefaultValue": false, "operations": [ "set" ]},

Project-B

https://emarsys.jira.com/rest/api/2/issue/createmeta?projectKeys=B&expand=projects.issuetypes.fields

-> it does not give me this custom field ID, therefore I cannot set it when creating a new issue via REST API.

The same issue persists if a new project is created and the existing custom field is being used, or if I simply clone a project.

Permissions-wise I don't see any issues (logged in with the integration user and checked if I can see the customfields assigned to both projects.

[Matthias Gaiser _K15t_]

Hi @Sandor Kocsis,

the createmeta endpoint only returns all fields on the create screen.

Could it be that the fields you are looking for are not on the create screen for that project?

Cheers,
Matthias.

[Sandor Kocsis]

nope, I am using the same fields for all screens.

The famous error I'm receiving:  "customfield_12850": "Field 'customfield_12850' cannot be set. It is not on the appropriate screen, or unknown."