Setting the Requst Type of a newly created Issue via remote API

Peter Androutsos

I have been able to successfully create an issue using the REST api (rails gem) on my JIRA Service Desk instance (cloud).  I have also been successful in setting the reporter, but I have noticed that although the customer has been set, the issue does not show up on the customer's request list.  I readily figured out that the problem is that the request type was not being set.

 

The project that I am using has the issue type mapped to a specific request type.  Furthermore, the Request Type field has been added to the create issue screen.  In addition, I have manually set another issue to include the appropriate request type, and determined the request type field to be 'customfield_10047'.  

 

With all this said, I have been very unsuccessful in setting the Request Type during creation.  The first semi-sucessful attempt resulted in the following error:

 

errors:

    customfield_10047: Operation value must be a string

 

 

This occurred when I was passing more complex information about the request type (so as to mirror an existing issue).

After this, the closest I managed to getting a semi-valid response is when the server was when using a pure string.  In this case, the server responded with:

 

errors:

    customfield_10047: Invalid customer request value

 

 

I've tried setting the string value to the id of the request type "97", and I've also tried setting it to the exact string value of the Request Type, namely "Purchase Request", but no matter what I enter, I get an error.

 

Any ideas on how this value can be set appropriately?

 

Dario B

Hi @Peter Androutsos ,

It  took a bit of research and testing but I am happy to say I managed to make this work in Jira Cloud as well. Also, I am adding this as a new answer so that if you like it you can accept it as the solution for this question.

The way to achieve what you are asking for is actually explained in below KB for Jira Server:

• How to set Request Type when creating an issue via REST API using /rest/api/2/issue endpoint

 

However, since in Cloud you do not have access to the Database, you cannot get the request type KEY from the  AO_54307E_VIEWPORTFORM table as explained in above KB, but you will have to use the following REST API endpoint instead:

• https://YOUR_HOSTNAME/rest/servicedesk/SERVICE_DESK/servicedesk/request/ISSUE/request-types

Calling to the above endpoint (or pasting it in the browser) with a correct issue ID and the correct service desk ID for the associated issue will result in JIRA returning a JSON response containing all customer request types within the service desk, including the Key.

 

Please notice that this is an internal endpoint not officially documented that can change without prior notice. Indeed we have the below Feature request opened in our system to have the official REST API endpoint to include the request-type key to which I have just added the workaround:

• JSDCLOUD-4917: The REST API endpoint /rest/servicedeskapi/servicedesk/{serviceDeskId}/requesttype should include the request-type Key in the response

 

You may want to vote and watch the above feature request so that you will get notified in case of any update. The  feature will be addressed according to the Implementation of New Features Policy.

 

Let me know if this helps.

 

Cheers,
Dario