CSV Import Unable to Import SubTasks as Issue ID no longer available to map to
Asked by Steindl_ Calman:

I regularly bulk import a template of tasks/subtasks in my jira project.

My CSV file has the following:

Summary,Issue Type,Issue id,Parent id,

test1,Task,1,,

test2,Task,2,,

summaryname subtask A,Sub-task,,2,

summaryname subtask B,Sub-task,,2,

This used to successfully create two SubTasks beneath the "test2" Task.

This has recently stopped working for me as when i go into the import menu; in the mapping fields page; the "Issue ID" field is no longer available to map to.

Thus, when i do the import, the subtasks do not get created as the parent Issue ID was not imported.

I am unsure what to try next; everything i have found says my csv file has the correct structure and I havent actually changed anything. Was there an update recently for Parent relationships in JIRA?

Any suggestions how to bulk import Tasks AND SubTasks simultaneously in JIRA cloud now?

![missing id field.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/342515iB6000CCEDEE1D78C/image-size/large?v=v2&px=999 "missing id field.jpg")

**Validation Test Results**

![validation.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/342517iB4EB7B2D7B774996/image-size/large?v=v2&px=999 "validation.jpg")

**Other Information;**

Jira Project is company managed, software project.

I am using the CSV import from the Filter/Search screen menu.


Answers:
author: Luka Hummel - codefortynine
body: Hi [@Steindl_ Calman](/t5/user/viewprofilepage/user-id/5233416)

If you are willing to use a third-party app, you could try our app [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2788386) to replace your CSV templating process. With Deep Clone for Jira, you can clone a template project including settings and issues, even to other Jira instances.

You can find more details on how to use Deep Clone for templating [here](https://documentation.codefortynine.com/deep-clone-for-jira/article-a-story-about-working-with-template-issues?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2788386).

This could help you streamline your import process and overcome the current limitations you're experiencing with the standard CSV import method.


author: Samuel Gatica
body: Hi [@Steindl_ Calman](/t5/user/viewprofilepage/user-id/5233416)

Try going to Settings \> System \> External System Import and do the import through that path instead of through the Filter/Search function.

Also, If you are trying to import Sub-tasks where their parents already exist, you do not need to import those parents as well. You only need to have an empty "Issue ID" column.

*** ** * ** ***

Example:

Parent Id, Issue Id, Summary, Issue Type

ABC-123,,"This is the summary",sub-task

ABC-123,,"Second subtask",sub-task

*** ** * ** ***

Yu can leave the "Issue Id" column empty.

Hope this helps

Best regard

Sam

comments: author: Steindl_ Calman
body: Hi Sam,

Thanks for your answer!

To clarify; I am trying to import new Tasks and new SubTasks.  
(so they don't have ABC-123 numbers yet).  

I am in a company managed JIRA project. This is what i get when I click on Settings.   
***Is there a different settings menu I am meant to be using?***   

![Settings menu.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/343076i4D34944AB55FBD36/image-size/large?v=v2&px=999 "Settings menu.jpg")


author: Samuel Gatica
body: Hi [@Steindl_ Calman](/t5/user/viewprofilepage/user-id/5233416)

Please check this post [import a list of issues including sub tasks in one import](https://community.atlassian.com/t5/Jira-questions/import-a-list-of-issues-including-sub-tasks-in-one-import/qaq-p/1430225)

*** ** * ** ***

See [Import data from a CSV file](https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html)

I'm not sure the sub-task section is too well written, as a lot of people seem to struggle with it, but this is a less fussy example of a file that will create 5 issues, two tasks, and 3 sub-tasks:

summary, issue id, parent id  
story1, 1,,  
subtask-1-1, 4, 1  
story2, 8,,  
subtask-2-1, 16, 8  
subtask-1-2, 32, 1  
Note that the issue id will be imported into "external id" as well, and the "parent id" is not imported directly, because it's only used to make the parent/sub-task link. Also, you'll need some other columns for issue type etc. I really did build that file to show you the parent/sub-task structure, nothing else

*** ** * ** ***

Hope this helps!

Best regards

Sam


Tags: cloud

jira-cloud