Unable to get the issue metadata using jira on premise

[Saurabh Bhandari]

I am using jira on premise and trying to get metadata for creating an issue as per this atlassian doc :
https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/

Url used : http://localhost:8080/rest/api/2/issue/createmeta?projectKeys=DEMO&expand=projects.issuetypes.fields

Response : 

{

    "errorMessages": [

        "Issue Does Not Exist"

    ],

    "errors": {}

}
So I am figuring out an API for jira on premise which will provide metadata for creating an issue.


Also, When i am using that endpoint for the jira cloud , It is working fine 
Url used: https://{host}/rest/api/3/issue/createmeta

Response :
 

[Jannik Arndt]

Hey Saurabh!

Thanks to your post I looked at the docs at https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/ and found the following:

Note that the createmeta resource has been reported to cause issues especially on larger instances. These issues have involved the size of the response or Jira running out of memory. That is why we decided to remove this endpoint in Jira 9.0.

The page is now split into "before 8.4" and "after 8.4".

Here they propose three new endpoints as replacement:

• http://localhost:8080/rest/api/2/project

• http://localhost:8080/rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes

• http://localhost:8080/rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}

Note that these seem to NOT work with Jira Cloud.

[Tom Penrose]

I am running on prem Jira DC 9.1.0 and these endpoints do not seem to work.  I am able to get projects but the second URL when requested with my project key or project id return "400 - Bad Request".  Any thoughts?

[Christoph Roll [Communardo]]

Same problem as @Tom Penrose - different error on DC v9.4.3 though:

Via Browser:

SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data

Via CURL: Nothing at all

[ghanshyam]

Same problem for on prem 9.4

[Jared Kells]

Hey Tom,

I've seen 400 responses with no error messages from those endpoints when the requesting user doesn't have permission to create issues in the project.

[Pavel]

That was the solution for me at least. I found out, that a call to 

https://myjiradomain/rest/api/2/issue/createmeta/PKEY/issuetypes?maxResults=5000

with a admin user returned 400.

Once I added the admin user to the project and assigned a role to him, which allows him to create issues in this specific project, the call was possible and successful. 

Thanks for the hint!