Can you Import subtasks using the "Import Issues from CSV" located in the Issues menu

[nkmori_rtx_com]

I need to have users be able to do a bulk import of subtasks.  I can import subtasks using the admin external Import, but I need users without admin privileges to be able to bulk import subtasks.  When I tried doing a bulk import of subtasks the error stated that the issue type was not provided for the subtask.  However when you use the "Import Issues from CSV" issue type and Issue key are not columns that you can identify in the mapping file.  Can you not use "Import Issues from CSV" to bulk import subtasks?  If you can use this functionality how do you setup your csv file to map correctly since issue type and Issue key are not available using Import Issues from CSV functionality

[Mary from Planyway]

Hi @nkmori_rtx_com 

It's Mary from Planyway 

In Jira, the "Import Issues from CSV" feature is primarily designed for importing standard issue types, such as tasks, bugs, or stories. When it comes to importing subtasks, the process is a bit more complex due to the hierarchical nature of subtasks being linked to their parent issues. The error you encountered regarding the issue type not being provided for the subtask suggests that Jira is expecting additional information to establish this hierarchy.

Here's a general approach to set up your CSV file for importing subtasks:

1. Include Parent Issue Keys: Your CSV file should include a column that specifies the parent issue key for each subtask. This is crucial because each subtask needs to be associated with a parent issue in Jira.

2. Specify Issue Types: Even though the "Import Issues from CSV" interface might not have explicit fields for 'Issue Type' or 'Issue Key', these can be included in the CSV file as columns. You should have a column for 'Issue Type' where you specify 'Sub-task' (or your equivalent subtask issue type name) for each subtask.

3. Map Fields Appropriately: When you go through the import process, Jira will allow you to map the columns in your CSV file to fields in Jira. Ensure that the column for the parent issue key is mapped to the 'Parent ID' or equivalent field in Jira, and the issue type column is mapped to the 'Issue Type' field.

4. Format and Data Consistency: Ensure that the data in your CSV file is consistent with what Jira expects. For example, issue keys should be in the correct format (e.g., PROJ-123), and user names or other fields should match their values in Jira.

5. Permissions: Ensure that the users who are performing the import have the necessary permissions. They need to have the 'Create Issues' permission in all relevant projects. If they don't have administrative privileges, you might need to adjust the project permissions temporarily or find an alternative method, such as using a Jira administrator to perform the import.

6. Testing: Before doing a bulk import, test the process with a small number of issues to ensure that the mapping is correct and the subtasks are being associated with the correct parent issues.