"issuetype":"issue type is required" on rest API issue creation

Guy Walker October 22, 2019

Using the Rest API to create jira tickets (for non Jira Users to submit issues).

 

I'm using the following JSON:

{
    "fields": {
       "project":
       { 
          "key": "FR"
       },
       "summary": "[entry.summary]",
       "description": "[entry.details]",
       "issuetype": {
          "name": "NEW FEATURE"
       }
   }
}

I've also tried NEW FEATURE as Regular Case and using 

 

"issuetype": {
          "id": "2"
       }

I get the following response

{"errorMessages":[],"errors":{"issuetype":"issue type is required"}}


Any pointers on where I'm going wrong?

1 answer

0 votes
Sebastian Krzewiński
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 22, 2019

Hi @Guy Walker 

 

It look like you add wrong issue type name or id.

Please list all issue types and check if you use correct name or id (<JIRA_url>/rest/api/2/issuetype)

 

Regards,

Seba

Guy Walker October 22, 2019

Hi Seba,

The only issue time I'm using in this specific FR Project is New Feature:

Screenshot 2019-10-22 at 15.36.58.png

I'm pulling the ID number from the Issue Type Edit URL:

https://jira.12345.com/secure/admin/EditIssueType!default.jspa?id=2
Sebastian Krzewiński
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 24, 2019

Hi

 

What url you have in your request?

 

Seba

Guy Walker October 25, 2019

I'm actually using a confluence plugin but it seems to be using https://jira.lucidworks.com/rest/api/latest/issue/ 

Like Jonas De Nadai likes this
Namy Namrata
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 16, 2024

Provide an issue type as in Bug, Story, Task or Epic

E.g.: 

"issuetype": {
          "name": "Bug"
       }
This will solve the error

Suggest an answer

Log in or Sign up to answer