This question is in reference to Atlassian Documentation: Importing data from CSV
How can I define Issue ID and Parent ID before CSV import procedure to avoid cases with duplicating of issues?
I mean case when you are trying to upload issue with Issue Id which already exists in JIRA.
Thank you.
You don't. If you already have a existing key, the import has to assume you are updating existing data, not creating a duplicate.
Are Issue ID and Parent ID used only for issues import from CSV?
When I tried to upload same CSV file with one Task and three sub-tasks in it two times in the row I found that second import process has created sub-tasks in already existed(imported in first try) Task.
No, sorry, I think you're misunderstanding what the importer will do.
Let's say that the important fields in here are
If a record has no issue-id or parent-id, the importer has no information about existing data, so it will try to create a new record
If a record has an issue-id, then the importer will check to see if it can find that ID in the target system. If it can, then the data must be an update of fields. If it can not, then it has no information and has to assume this is a new issue
If a record has a parent-id, then the system will do the same as above, but working on the assumption that the data is for a sub-task instead
Thank you, Nic.
So if I would like to import several tasks with sub-tasks inside and I would like to avoid case when existed data will be updated because of existed Issue Id will be defined in CSV file. How can I proceed with this? I have to enter Issue ID and Parent ID to CSV file for link between sub-tasks and parent tasks. But I don't know whether entered Issue ID is unique.
Hi,
Has there been any follow up to @Tyler Yoder query from May 15, 2018?
It seems counter-intuitive that the issue ID must be unique for a project, as that is what the Issue Key would used for. Using the issue/parent ID is the only way to link sub-tasks to their parent.
Creating this restraint on the Issue ID means that any particular user importing data would have to keep track of the last ID added into the system, which adds an extra level of complexity to manage.
I think you have missed the point of the conversation above, but that would not be a suprise as this is not obvious and I do not think the language in the docs helps much.
Put simply, the Jira issue key and the Jira issue ID have nothing to do with the ID in the import file.
The import-issue-id does not have to be unique for the project, just for the import file (although if you do many imports, it should be unique to the issues in the import file).
A user has absolutely no need to track the last ID added. Jira handles all of that.
The most simple example I can give of a CSV to show how this works:
+ CSV ID + Jira Key + Parent ID + Summary|137 | | | A new issue|42 | | 137 | A new subtask of 137| | ABC-123 | | An edit to existing issue ABC-123
It looks like you're new here. Sign in or register to get started.
