I have a CSV file with one issue and a number of subtasks defined. If I import that exact same file twice (I change the issue summary for the second import just to keep track of it) it will compain the second time that the issue already exists (even though summaries are different) and then it will add duplicates of the subtasks to the already existing issue.
I am not sure if this bug is resolved or if there is a workaround?
If I use the same csv file (same data) to import issues with sub-task, it fails second time. JIP complains that sub-task already exist with the IssueID i have provided. This is a bug. The IssueID is being stored as External Issue ID.
As a workaround:
I keep track of the all ISSUE IDs I have used so that I do not get the error.
Not the issue keys.. but the issue IDs are the same.. I am trying to create new issues with subtasks.. and I believe that if we do not map the Issue Keys, JIRA importer plugin should create the issues.. and for sub-tasks.. it should not matter if we use the same Issue IDs and Parent IDs as JIRA importer plugin should not save these Issue IDs in the database.. those should be used only for import purpose.. else it would be hard to track the issue IDs which has already been imported..
It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs