Issue Summary

When conducting an assets import, integers representing a datetime parsed using Windows NT time format do not retain the two most significant digits of the year; any year is set to 20xx, even if the provided year does not match the 20 prefix.

Steps to Reproduce

• Adjust your Jira look and feel datetime format to have a four digit year (to allow you to see the incorrect year)
  

• Create a new empty assets object schema and assets object type, which includes a new attribute of type 'DateTime' 

• Construct a csv with the following content

name,integer_datetime_representation
"Test Object",638292024000000000

(Representing a date in year 3623 when parsed using WindowsNT datetime format)

• Create a new csv import configuration for the new assets object schema, uploading the above csv file (all other configuration can remain unchanged).

• Create an object type mapping to the new csv import (all configuration in the create modal can remain default), set data locators and matching assets attributes after creation.

• Run a sync.

• Review the newly imported assets object.

Actual Results

Imported assets object shows a date in 2023.

(note this server is configured with UTC timezone)

Expected Results

Imported asset object should show a date in 3623.

(note this server is configured with timezone offset of GMT +09:00)

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: