JSON Import - How to add a Request Type

[Bryton Salisbury]

We're trying to mass import tickets from another ticketing system, but I can't for the life of me figure out how to map to a 'Request Type' within JSM.

What does it take to get this field to populate using a JSON import?

I've tried many combinations of using field[], customFieldValues[], customfield_10010: but I can't get anything to actually work.

[Julien Saab]

Hello,

I'm going to consolidate my findings and what I did in this answer.

First of all, to import a custom field we need to know its type. There's an API that retrieves the fields that are available in the Jira cloud instance. If you're logged in to your Jira instance on a browser, then you can simply go to https://{instanceName}.atlassian.net/rest/api/3/field, which will return a JSON list of fields.

If we search for the "Request Type" field we get:

From that we need two things:

• The custom field ID: customfield_10200
• The custom field internal type: com.atlassian.servicedesk:vp-origin

Now, we can construct our sample JSON import file:

{
    "users": [
        {
            "name": "user1",
            "email":"john.doe@mydomain.com"
        }
    ],
    "links": [],
    "projects": [
        {
            "key": "PJK",
            "issues": [
                {
                    "externalId": "OLD-123",
                    "summary": "Test ticket",
                    "description": "This is a ticket description",
                    "reporter": "user1",
                    "status": "Resolved",
                    "resolution":"Resolved",
                    "issueType":"Bug",
                    "components": [
                        "Component 1"
                    ],
                    "created": "2025-11-12T12:34:02.987+0200",
                    "updated": "2025-11-13T15:12:43.458+0200",
                    "assignee": "user1",
                    "history": [
                        {
                            "author": "user1",
                            "created": "2025-11-13T15:12:43.458+0200",
                            "items": [
                                {
                                    "fieldType": "jira",
                                    "field": "status",
                                    "from": "1",
                                    "fromString": "Open",
                                    "to": "5",
                                    "toString": "Resolved"
                                }
                            ]
                        }
                    ],
                    "customFieldValues": [
                        {
                            "fieldName": "customfield_10200",
                            "fieldType": "com.atlassian.servicedesk:vp-origin",
                            "value": "22"
                        }
                    ],
                     "comments": [
                        {
                            "body": "We've started working on this request",
                            "author": "user1",
                            "created": "2025-11-12T12:41:31.125+0200",
                            "properties":[{"key":"sd.public.comment","value":{"internal":"false"}}]
                        }
                    ]
                }
            ]
        }
    ]
}

Notice how in the customFieldValues array I created an object with the following mapped fields:

• fieldName: This is equivalent to the id of the custom field that we got from the API

• fieldType: This is equivalent to the schema.custom property of the custom field that we got from the API
• value: I got this value by going to an already existing issue and getting it from the API. (I've explained it below)

To get a sample value for the custom field: 

• Assume the issue has the key PJK-123 and it has a request type that is similar to the one you want to reference.
• Then using the API https://{instanceName}.atlassian.net/rest/api/2/issue/PJK-123?expand=names you'll get a JSON object containing most information related to that issue. 
• Search for the customfield_10200 JSON object, and you'll find the id attribute which is the value that I used.
  

Hope this helps!

[tkeyrouz]

wow, it helped a lot. such a life savior! thanks man.

[Marcelino Abou Haidar]

This is brilliant! A perfect, complete solution. Thank you for this miracle!

[Kai Becker]

Hi @Bryton Salisbury 

welcome to the community and thanks for your question.
You were almost their with your past tries, but the input value is a little more complicated.

It is a regular custom field like "customfield_10202",  but the value is a combination of the project key and the request type name, like so: "its/getithelp"

A detailed guide to get these values can be found here.

[Francis Batilo]

Hi @Bryton Salisbury

I needed the same idea as you and I found the solution to your question. I know this is more than a year late, but this is the field type the you need to update your Custom Request Type Field

"fieldType": "com.atlassian.servicedesk:vp-origin",

For reference, you can find this information under your inspect page and then find 

1. field-config/src folder
2. open index.tsx and then find the export const command for the field that you're looking for (e.g., export const REQUEST_TYPE_CF_TYPE = 'com.atlassian.servicedesk:vp-origin' as const;).

It's been more than a year, but I hope this answer finds you and it helps you.

Cheers,

Francis

[Maximiliano Julio]

Hi Francisco, how are you?

I am experiencing the same problem.
Could you provide more detail about your solution you found? I'm sure I will find it very useful

Regards