What are the use cases for Parent ID vs. Parent Key?

Question

I've exported several approved subtasks with all available fields. Within the fields is "Parent ID" with a 5-digit code. I've attempted to use this code to mass import additional subtasks associated to the same parents as the approved subtasks mentioned above. When doing this, the system does not accept the 5-digit code. Instead, it wants the more traditional key (i.e. KEY-123). I don't understand the purpose of the 5-digit code if it can't be used in the Parent ID field upon import. Is there some way to easily convert the 5-digit code into the key that the import wants?

Petter Gonçalves · Accepted Answer

Hello Matt,

Please, allow me to clarify the difference between both fields:

The parent ID is a general issue identifier field which is immutable, while the Parent key can be changed by the user (Moving issues to a different project, importing a different value, etc).

About the error you are facing, please check if you are mapping your Parent ID and Issue ID fields of your sub-tasks as described on this documentation:

Creating sub-tasks

You can create sub-tasks of issues by:

* Adding two columns to your CSV file with the headings "Issue Id" and "Parent Id"
* Ensuring each regular (non sub-task) issue is given a unique (sequential) number in the "Issue Id" column. Do not include any value in the "Parent Id" fields for regular issues.
* Referencing the unique "Issue Id" number of the regular issue in the "Parent Id" column. Do not include any value in the "Issue Id" fields for sub-tasks.

In this example, the fourth issue will be a sub-task of the second issue if you match the "Issue Id" and "Parent Id" fields in your CSV file to the corresponding issue and parent ID fields in Jira:

IssueType, Summary, FixVersion, FixVersion, FixVersion, Component, Component, Issue ID, Parent ID, Reporter
Bug, "First issue", v1, , , Component1, , 1, , jbloggs
Bug, "Second issue", v2, , , Component1, Component2, 2, , fferdinando
Bug, "Third issue", v1, v2, v3, Component1, , 3, , fferdinando
Sub-task, "Fourth issue", v1, v2, , Component2, , , 2, jbloggs

Let me know your results.