-
Bug
-
Resolution: Cannot Reproduce
-
Medium
-
1
-
Severity 3 - Minor
-
0
-
Issue Summary
When importing comments to issues in Next-Gen projects an error is thrown using the External System Import.
Steps to Reproduce
- Create a CSV file containing Summary,Issue key,Issue id,Comment,Issue Type, Parent
- Try to import the CSV file.
Expected Results
The fields are going to be updated and the comment will be imported.
Actual Results
The following error is thrown:
Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state: At least one given IssueParentAssociations must not be empty!
Workaround
What happens is that the importer will look for a Parent Association for the imported issue and if it does not exists it fails. To work around the behavior create a new Epic and add all the issues into it and then perform the import mapping the Parent -> Parent ID with an empty value.
- relates to
-
JRACLOUD-82657 Team-managed projects do not support CSV imports
- Gathering Interest
[JRACLOUD-81967] When importing comments to issues in team-managed projects an error is thrown
Do the watchers of this ticket still experience this issue? I am not able to reproduce it. This was my CSV:
Summary,Issue key,Issue id,Comment JRACLOUD-81967 team-managed issue with comment,GSWNG-41,11206,2024-01-29 13:42;70121:f4426d6e-009f-460d-a729-cdd7d64597fb;JRACLOUD-81967 comment2
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
We have built a script as a workaround to create the Epic/Child relationship of team managed projects via REST API by reading the original imported CSV file:
Thanks jsilveira 
Again, this doesn't fix the problem of not being able to edit the issues from Team-managed projects via CSV, yet, it allows you to create the Parent/Children relationship of Epics and the respective children standard issue types.
As I did not receive any responses to this comment I am closing this ticket.
If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.