Issue Summary

This is reproducible on Data Center: yes

If we create an Asset object through Jira issue post-function while copying any JIra-date type field to the object date attribute, it works fine if the year is on or before year 2044. If the year is 2045 onwards it changes to 1945 and so in the object attribute. Refer to the screenshots for more details.

Steps to Reproduce

1. Create an Asset ObjectType with a date attribute. (Screenshot 1)
2. Create another Date CF2 and map to the same test project (for example I used system-field "Due-date")
3.  Use Assets post function "Create an Assets Object from a Jira Issue" on any transition after the issue is created
4.  Map the issue field Date CF2 with teh Asset Date attribute. (Screenshot 2)
5. Publish the workflow
6. Create an issue and choose the value in Date CF2 after 2044. (Screenshot 3)
7. Perform the next transition where Asset object was supposed to be created
8. Verify the Asset object, it will show 1949 ((Screenshot 4))

Expected Results

Asset Date attribute should be reflecint correct data in this example 2049

Actual Results

Asset object has the Date attribute as 1949

Workaround

N/A