I imported an issue from a csv file, but some subtasks are not imported.

[KOBAYASHI HIROKAZU (JIT TRI)]

I imported an issue from a csv file, but some subtasks are not imported.
I exported all issues from another project and imported the csv file into another project, but some subtasks are not imported.
319 issues are reflected in only 250.
No errors were detected in the validation performed prior to import.
Why?

[Asha Goyal]

Hello @KOBAYASHI HIROKAZU (JIT TRI) 

 You are trying to import the subtask via CSV, and for that it is mandatory to provide a parent issue key. Every subtask must have a parent issue, and without them, subtask cannot be created in Jira. 

Make sure that either parent is already exist into the system, and if not please break the CSV into two parts. In the first go Import the parent first, take the parent Issue key from Jira and then import the subtask subsequently.

Tip -- Make use of label while importing to identify the recent issues imported.

I hope it helps.

Please accept my answer if it found useful.

Thanks

[Noah - Devsamurai]

Hello @KOBAYASHI HIROKAZU (JIT TRI) 

It appears that you're facing an issue where some subtasks are not being imported despite using the CSV import feature in Jira. Here are some possible reasons for this discrepancy:

1. Data Accuracy: Check the CSV file to ensure that the subtasks are correctly formatted and all necessary fields are included. Any missing or improperly formatted data could lead to certain subtasks being skipped during the import process.

2. Issue Linkage: Subtasks might not import properly if there are issues with linking them to their parent tasks. Ensure that parent-child relationships are clearly defined in the CSV file and handled correctly during the import.

3. Permissions: Verify that the user performing the import has sufficient permissions to create subtasks in the destination project. Restrictions or permissions set up in the project might prevent certain subtasks from being imported.

4. Configuration Settings: Review the project configuration settings, including issue types, workflows, and field mappings. Misconfigurations in these settings could affect the import process and lead to subtasks not being imported as expected.

5. Data Integrity: Double-check the source project to ensure that all subtasks are included in the export file. It's possible that some subtasks were not exported correctly or were missing from the export.

6. System Limits: Check if the import process exceeds any system limitations, such as maximum file size or the number of issues that can be imported at once.

7. Logging and Debugging: Enable logging or debug mode during the import process to gather more detailed information about any errors or issues encountered. This could help pinpoint the specific reasons why certain subtasks are not being imported.

Hope this can help. 

Warm regards.