JIRA REST API returns no editmeta field data for some identical projects

[Fred Raines]

Jira Software 8.2.3 - and perhaps earlier versions

Windows Server 2012 R2

MSSQL

Several projects were created with shared configuration that has custom issue types, fields, and screen schemes.  All projects work identically from the web interface.

An API call (via curl) to extract the editmeta field information for the same issue type and screen type (it is the screen used for edit), returns the field for some projects but not others.  The Jira administrator credentials are used for all the API calls.

Calls that succeed return lots of field data.

Calls that don't return field data result in this output: ... 57{"fields":{}}

None of the fields are hidden on the projects that return no information.

Suggestions

----------------------------

Update

It turns out that they were not in fact identical.  The projects returning data had our jira administrator set in at lease one role.  The solution was to add the jira-administrators group to the issues premission scheme for Edit issues.

I consider this resolved.

[Stephen Sifers · Accepted solution]

Sourced from above, adding the solution:

@Fred Raines 

Update

It turns out that they were not in fact identical.  The projects returning data had our jira administrator set in at lease one role.  The solution was to add the jira-administrators group to the issues premission scheme for Edit issues.

I consider this resolved.