/rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes no longer working on Jira Cloud (wrong post, should be "createmeta: copy operation entry prevents JIRA REST Java Client from working)"?

Hi,
When I try to get createmeta data via the
/rest/api/latest/issue/createmeta/{projectIdOrKey}/issuetypes
API call I get a 404 error for both, project key and id.
The message is: null for uri: https://MYSITE.atlassian.net/rest/api/latest/issue/createmeta/10000/issuetypes

Strangely enough the call: /rest/api/latest/issue/createmeta
without the project Id works correctly …

The problem seems to have appeared on December 16, about 0h UTC

Is this a known bug or a new feature?
Any estimates if/when this will be fixed (we need this API call for our Jira integration).

All the best
Josef

Hello @JosefMoser

There is no such endpoint with that syntax in either the v2 or v3 REST APIs of Jira Cloud. If you refer to the documentation, you’ll see the syntax for the Get create issue metadata endpoint is described as:

GET /rest/api/latest/issue/createmeta

…and it accepts the parameters projectIds, projectKeys, issuetypeIds and issuetypeNames

You seem to have jumbled up Jira CLOUD and Jira SERVER. It is Jira SERVER’s v2 REST API that has an endpoint with the syntax GET /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes

Hello @sunnyape

Yes, sorry, I was on the wrong track when investigating the problem.

We use /rest/api/latest/issue/createmeta as a fallback for cases where /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes is not supported.

The problem is that /rest/api/latest/issue/createmeta suddenly returns “copy” for project/issuetypes/fields/{fieldName}/operations which causes the JIRA REST Java Client to throw : “java.lang.IllegalArgumentException: No enum constant com.atlassian.jira.rest.client.api.domain.StandardOperation.COPY”

We reported this as https://support.atlassian.com/requests/JST-830948/

@JosefMoser
Same issue mention here: https://community.atlassian.com/t5/Jira-questions/No-enum-constant-com-atlassian-jira-rest-client-api-domain/qaq-p/2218709#U2233187

Did anyone find a solution to this issue. This is still happening with our Jira Rest Client too and surprising how you guys were able to overcome through this. I didn’t find an patch in JRJC source code too - Bitbucket

Belated welcome to the Atlassian developer community @JeevanKumarChamarthi,

And for the benefit of @lostpradise @JosefMoser, there is a recent announcement about Create Issue Meta Endpoint Deprecation where one of the replacement endpoints does perform “issue types by project”:

Specific to @JeevanKumarChamarthi’s question about JRJC, I hope you aren’t using that with Jira Cloud. It looks clear to me that library is being maintained for Server/DC but not for Cloud.