Did someone change the REST API for /rest/api/2/issue/ABC-1?expand=editmeta?
It used to provide a list of editable fields. Now, the editmeta value in the response is just {"fields":{}}.
Hello @david.pinn
That endpoint is working just fine for me. Are you including the id or key of the issue with the request?
https://{instance}/rest/api/2/issue/{issueIdOrKey}?expand=editmeta
Yes, I am. I’ve amended original question accordingly.
Maybe it’s just the circumstances in which the editmeta data are non-empty has changed. I’ve yet to establish that. All I know for sure is that, for at least some issues, the list of editable fields used to be non-empty and now it’s empty. And I mean issues that haven’t changed either in their content or their permission context.
If the issues in question have identical permissions but different behaviours, then, off the top of my head I can’t think of a circumstance; all issue types invariably have fields, and those fields are invariably editable.
All I can think of is that you’re using OAuth credentials with granular scopes and haven’t used the read:issue-meta:jira scope in certain scenarios.
I’ll leave it with you to investigate further.
Fair enough. Thank you for looking into it for me.
At least, if other developers encounter the same problem, they may find this post as an indicator that they are not alone.