Issue Summary

If a user attempts to import a datetime data store in Unix epoch format into a date or datetime type attribute in Jira Asset, the year in the attribute value of the imported object is incorrect. This issue occurs only when the date and datetime formats specified under the "Look and Feel" system configuration are set to "dd/MMM/yyyy" and "dd/MMM/yyyy h:mm a," respectively.

Steps to Reproduce:

1. Update the date and datetime formats in the "Look and Feel" system configuration. Set the formats to "dd/MMM/yyyy" for the date and "dd/MMM/yyyy h:mm a" for the datetime.
2. Create a temporary database table to import data from. This table should include a bigint type column to store timestamps in Unix epoch format (e.g., 638292024000000000).
3. Create an object type that contains at least one datetime type attribute.
4. Set up a database import process and map the newly created temporary table to the object type created in the previous step.
5. In the object type mapping configuration for the import, map the database column containing the Unix time to the datetime type attribute of the object type.
6. Run the import and verify the value of the datetime type attribute in the imported object.

Expected Results

The datetime attribute should have correct datetime
eg: 01/Sep/2023 10:00 pm

Actual Results

The datetime attribute has incorrect year
eg: 01/Sep/3623 10:00 pm

Workaround

Update the date and datetime format under ⚙️ > System > "Look and Feel" configuration to "dd/MMM/yy" and "dd/MMM/yy h:mm a".

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