The GET /rest/issue/createmeta endpoint was removed from the API in Jira 9.

As per Jira Software 9.0.x release notes,

The GET /rest/issue/createmeta endpoint allowed you to get metainformation on everything in Jira: projects, issues, etc. This opportunity had a big impact on Jira performance. That's why, we decided to remove it completely in Jira 9.0.

Instead, you can use the following endpoint to get metainformation on one project at a time:

GET /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes
GET /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}

However, a few customers have been using the GET /rest/issue/createmeta endpoint extensively in their Jira application for integrations and other purposes without observing the impact on Jira's performance.

They would like to continue using the GET /rest/issue/createmeta endpoint or provide a useful alternative. For example

1. It would be great if we can have a Dark Feature through which users get an option to use the GET /rest/issue/createmeta endpoint.
2. Providing an &expand= query parameter to Get create metadata issue types for a project that returns Field information
3. Providing a new endpoint between the two new ones /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/ that returns the Fields and other data for one Project.

Alternatives include using

• https://docs.atlassian.com/software/jira/docs/api/REST/9.17.0/#api/2/customFields-getCustomFields