Existing issue is not update via CSV Import

Project Leader September 5, 2023

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.

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 5, 2023

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.

Project Leader September 5, 2023

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 

my csv issue key.png

--> I also map that

my csv mapping.png

 

2. From where did you access the import functionality? Administration > System > External System Import.

--> System > External System Import.

access to Import.png

 

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 ?

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 6, 2023

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.

roberto_sc April 16, 2024

@Project Leader Did you manage to get this working? I'm having the exact same issue.

roberto_sc April 16, 2024

@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.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 17, 2024

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events