JIRA Import Issue Links using JSON importer


I am trying to test JSON importer for the links or issuelinks using the following JSON data structure. But I don't know what do "sourceId" and "destinationId" mean? Are they the issue numbers? How does it work for cross projects? What are the valid values for "name"?

"links": [
"name": "sub-task-link",
"sourceId": "2",
"destinationId": "1"
"name": "Duplicate",
"sourceId": "3",
"destinationId": "2"

Your help is much appreciated.

1 answer

1 accepted

sourceID and destinationID refer to the issues being linked to each other. The number used to represent the issues being linked corresponds to the externalID. For instance, in your first example, the issue with externalID = '2' is the subtask (source) of the issue with externalID = '1' (the parent issue). This key is unique, and should allow you to link any issues together (even across projects).

    "status" : "Open",
    "reporter" : "bob",
    "issueType": "Sub-task",
    "created" : "P-3D",
    "updated" : "P-1D",
    "summary" : "Sub-task",
    "externalId": "2"
                    "priority" : "Major",
                    "description" : "Some nice description here\nMaybe _italics_ or *bold*?",
                    "status" : "Closed",
                    "reporter" : "alice",
                    "labels" : [ "impossible", "to", "test" ],
                    "watchers" : [ "bob" ],
                    "issueType" : "Bug",
                    "resolution" : "Resolved",
                    "created" : "2012-08-31T17:59:02.161+0100",
                    "updated" : "P-1D",
                    "affectedVersions" : [ "1.0" ],
                    "summary" : "My chore for today",
                    "assignee" : "bob",
                    "fixedVersions" : [ "1.0", "2.0" ],
                    "components" : ["Component", "AnotherComponent"],
                    "externalId" : "1"

The "name" field corresponds to the types of links you can make (i.e. sub-task-link, Duplicate, Blocks, Incorporates, etc.)

Hope this helps!

Is it possible to link issues together using non-numeric, or alpha-numeric keys? 

For example: 

"links": [
"name": "sub-task-link",
"sourceId": "A",
"destinationId": "B"


    "status" "Open",
    "reporter" "bob",
    "created" "P-3D",
    "updated" "P-1D",
    "summary" "Sub-task",
                    "priority" "Major",
                    "description" "Some nice description here\nMaybe _italics_ or *bold*?",
                    "status" "Closed",
                    "reporter" "alice",
                    "labels" : [ "impossible""to""test" ],
                    "watchers" : [ "bob" ],
                    "issueType" "Bug",
                    "resolution" "Resolved",
                    "created" "2012-08-31T17:59:02.161+0100",
                    "updated" "P-1D",
                    "affectedVersions" : [ "1.0" ],
                    "summary" "My chore for today",
                    "assignee" "bob",
                    "fixedVersions" : [ "1.0""2.0" ],
                    "components" : ["Component""AnotherComponent"],
                    "externalId" "B"


I believe the externalID is an ID internal to JIRA, and will not work in the way you are describing. You can certainly make REST requests to recover each of these IDs but they are always returned as a numeric value.

I want to use a JSON export file to copy the full project content between two JIRA instances. The problem is that the issue links are not contained neither in a JSON export nor in a CSV export.

Is it really necessary to add the issue links manually and this data cannot be directly received from the source database (assuming the issue keys are equal on both sides)?

Suggest an answer

Log in or Join to answer
Community showcase
Maarten Cautreels
Posted Thursday in Off-topic

Friday Fun: What's your favourite beer/drink

As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...

285 views 38 9
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot