You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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 :
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.
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/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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.