I tried to update existing issues and create new issues via CSV import.
[Purpose of CSV import]
1. Update 2 existing issues --> update attribute of issue (e.g. due date, status )
2. Create 2 new issues
The result was failed.
Only new issues were created but existing issue was not updated.
How to update existing issue via CSV import?
Below is detail log of importing CSV files
2023-09-06 02:26:36,446 INFO - ------------------------------ 2023-09-06 02:26:36,446 INFO - Importing: Issues 2023-09-06 02:26:36,446 INFO - ------------------------------ 2023-09-06 02:26:36,446 INFO - Only new items will be imported 2023-09-06 02:26:36,552 INFO - External issue 10110 already exists as GOD-107, not importing. 2023-09-06 02:26:36,556 INFO - Importing issue: [externalId='autoid-3411940195770920728', summary='Refinement of Feature Update'] 2023-09-06 02:26:37,228 INFO - External issue 10105 already exists as GOD-102, not importing. 2023-09-06 02:26:37,233 INFO - Importing issue: [externalId='autoid--1641133955596348178', summary='Refinement of Requirement Update'] 2023-09-06 02:26:37,707 WARN - 2 of 4 issues have been skipped because they already exist in destination projects. 2023-09-06 02:26:37,710 INFO - 2 out of 4 issues successfully created 2023-09-06 02:26:37,714 INFO - ------------------------------
External issue 10110 and 10105 were skipped because there were in Jira project.
Hello @Project Leader
Did you provide the issue keys for the existing issues in your CSV file, and did you map that field during the import process?
From where did you access the import functionality? It could be accessed from the Create Issue dialog, from the "View all issues" page, or from Administration > System > External System Import. I'm not positive, but you may be able to update existing issue only when you use the External System Import. And you definitely have to provide the issue key as part of the CSV file, so that Jira knows which issues you're trying to update.
I would put the issues you want to update in a separate CSV file from the file that contains new issues you want to create.
1. Did you provide the issue keys for the existing issues in your CSV file, and did you map that field during the import process?
--> yes my csv file hase issue key
--> I also map that
2. From where did you access the import functionality? Administration > System > External System Import.
--> System > External System Import.
3. I would put the issues you want to update in a separate CSV file from the file that contains new issues you want to create.
--> I divided it into file with only existing issues and file with only new issues and then import only existing issues file. but failed again. Below is detail log.
2023-09-06 06:39:54,564 INFO - Only new items will be imported 2023-09-06 06:39:54,709 INFO - External issue 10110 already exists as GOD-107, not importing. 2023-09-06 06:39:54,716 INFO - External issue 10105 already exists as GOD-102, not importing. 2023-09-06 06:39:54,720 WARN - 2 of 2 issues have been skipped because they already exist in destination projects.
In that log, I can find "only new items will be imported" <-- Can I change this option from new one to existing one ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Don't include the Issue ID field. You need only the Issue Key field.
You must include the Summary field.
Otherwise include columns for only the fields you want to change in 1 or more issues. If you don't want to change the value in a particular issue, include the original value for that issue for that field.
I haven't used importing to update existing issues for quite some time, but based on other posts in the community it should still be possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill I'm having the same problem and tried to not include the Issue ID field. However, I'm updating the Parent field so it requires the Issue ID field to do a lookup while importing.
It doesn't allow me to proceed if I map the Parent and don't include the Issue ID.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It appears you started a new Question for your issue and you have received responses there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy ClaspillI tried to update a field in an existing ticket via "issues > import issues via CSV". Although I mapped the issue ID, got a new ticket at the end. What was wrong?
I couldn't find the access you mentioned above "Administration > System > External System Import".
Thank you so much in advance!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian community.
To get the widest visibility on your request for help, start a new Question by clicking the Ask a question option at the top of the community pages. Provide the details of your scenario including a sample of your CSV, and screen images of what you see when you try to navigate to the import function. If you think this post is relevant, include a link to it and explain the relevance.
Also review the Community Guidelines concerning Necroposting.
https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy ClaspillI posted a new request. Can you please have a look? :) https://community.atlassian.com/t5/Jira-questions/Cannot-update-the-existing-issues-via-CSV-Import/qaq-p/2960378
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.