Is updating existing issues via CSV import when their ID's are the same?
How can we import without duplicating the issue? It was working fine 3.0.x not working in 5.0.4.
Replies (4)
RE: Is updating existing issues via CSV import when their ID's are the same?
-
Added by Dorothy Valverde 7 months ago
Yes, it is possible to update existing issues via CSV import in Jira. To update fields in existing issues, the required fields are issueKey and Summary plus the fields you want to update. To update existing issues, your CSV file needs to contain a column that maps to Issue Key. If an issue exists for a given key, it will be updated. Your CSV file will also require the summary field.
To avoid duplicating the issue, make sure that the Issue Key field in your CSV file matches the Issue Key of the issue you want to update. If the Issue Key in your CSV file matches the Issue Key of an existing issue, that issue will be updated with the new information. If the Issue Key in your CSV file does not match the Issue Key of any existing issues, a new issue will be created.
RE: Is updating existing issues via CSV import when their ID's are the same?
-
Added by K S 7 months ago
Is it in Jira? I am asking in Redmine 5
RE: Is updating existing issues via CSV import when their ID's are the same?
-
Added by Holger Just 7 months ago
I'm not sure what the Jira bit is about...
The Redmine importers do not support updating existing issues (or other imported objects). The CSV import always creates new objects and does care about any existing data. If you want to udpate existing issues, you can use the REST API instead, see Rest_api for details as well as Rest_Issues for a description of the issues API.
RE: Is updating existing issues via CSV import when their ID's are the same?
-
Added by Harmony Kuhn 6 months ago
I also want to know it.