-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
29
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Lets say a user wants to import the QA_Contacts field from a Bugzilla instance. As this field cannot yet be imported as per this feature request: https://ecosystem.atlassian.net/browse/JIM-533
So the logical thing to do is to import the field separately via CSV import. The problem here is that the Updated field of the issue will be overwritten with the latest date. This is a big problem for customers who wants to preserve historical data on older, closed tickets.
Even if you manually specify the Updated field to a column in the CSV file, the CSV importer does not import those values and the Date Updated field will be set to the latest date, and not to the value you specified in the CSV import.
This happens because Jira considers the CSV import on top of an existing issue as an update to the issue itself and thus, puts current datetime in the updated date field.
The updated date field will reflect the value from the CSV if the issue is not present prior to the import.
- relates to
-
- Gathering Interest
- is duplicated by
-
JIM-998 Failed to load
- mentioned in
-
Page Failed to load
[JRASERVER-64492] CSV Import does not import the "Date Updated" field for existing issues
I've just tested "Modified Date" for 8.9.0 and it did not work.
When creating new issues via CSV import (Jira 8.8.1), I've found that, for me, Sub-Tasks accept the provided "Modified Date" while parent tasks (such as Stories) do not. No date parsing errors in import log, dates formatted identically for both issue types.
I am facing the same issue as Kevin, Tammy and Ingrid. And seriously, if "Modified Date" can't be updated using any of the imports then it shouldn't appear while mapping fields and also this should be mentioned explicitly in documentation or import screen that '"Modified Date" can't be updated and will always show today's date'.
We have to merge custom fields on 10k+ legacy issues that we imported, and I don't want to touch the updated field because we're not making any modifications to any of these issues. Putting today's date stamp in the updated field isn't really a workable solution. Why is the updated field available if it's not mapped and being honored to populate the data as specified?
An user messed up with import of resolutions and I need to reimport the data, but without change of Date modified. SO I NEED IT TOO.
I need this also. We are migrating from a cloud instance to hosted and want to retain the date updated. It simply replaces with today's date. No bueno.
Tested in 8.20.10 server version, Date modified didn't work using CSV.