-
Bug
-
Resolution: Unresolved
-
High
-
12
-
Severity 3 - Minor
-
38
-
Issue Summary
When performing an import from the bulk creation CSV import (on the create issue screen) and set the value for a Task and its sub-tasks on the CSV file, the import troughs an error about Subtask 'test CSV' doesn't have a valid Parent Id selection. Issue will not be created.
We got this same error in these scenarios:
- Setting an issue Id and parent Id arbitrary and the CSV file;
- Using an issue Id from an already created task in the project
Environment
Jira Cloud
Steps to Reproduce
- Create a CSV file with the Issue Id and Parent Id column;
- Use the non-admin CSV import (create issue screen > Import issue button);
- Mapp the columns of issue Id and parent Id
- Begin the CSV import
Expected Results
The import should create the Task and the Sub-task accordingly as in the CSV file.
Actual Results
The import stops with the following error:
Subtask 'test CSV' doesn't have a valid Parent Id selection. Issue will not be created
Notes
Workaround
A workaround will be run the CSV import through the External system import, accessible only by Jira administrators
[JRACLOUD-81997] The non-admin CSV Importer gives an error for the parent Id field
This is a major issue for our team, the workaround is not viable as we have 15,000 users in our instance and us admins cannot provide import help to all users who needs this functionality that used to work as expected.
Hello!
We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to fill out this survey. Your feedback will help us learn how we can improve your experience in importing data.
Survey link - https://forms.gle/NYNkmS92r96z42QV9
Thanks!
Prashanth M
Product Manager, Jira Platform
This is a huge problem. Even when I import using the admin importer, the sub-tasks are created with no parent link. If I open a sub-task and try and populate the parent link field with the correct issue, it tells me that issue doesn't exist. I am trying to import issues into a new project, and this is severely impacting the team.
How does one vote so that this issue gets resolved? Huge problem to something that is a basic need.
There is a workaround, not safe tho, when you can write a script that will raise these requests via api, but with api key of an admin. Also, it accepts data in JSON format not CSV, but overall I wonder why this acts like that. This feature worked perfectly for Jira Data Center.