Issue Summary

Customers try to edit the timezone of a field and set it on a data field using Additional Fields with smart values similar to the below. But the end result is not what's expected.

{
    "fields": {
        "customfield_10400": "{{now.setTimeZone("Asia/Kolkata")}}",
        "customfield_10401": "{{issue.created.setTimeZone("Asia/Kolkata")}}"
    }
}

This was only reproduced so far with the Asia/Kolkata timezone.

Steps to Reproduce

1. Create a rule for editing a Date Time field using Additional Fields;
2. Add the smart value structure as mentioned on the issue summary.

Expected Results

Field gets set with the Asia/Kolkata timezone (GMT + 5.5).

Actual Results

Field is getting set one hour earlier than what it is expected.

On the example above, it would be expected that the IST timezone field would be set as 10:30 PM, but it is being set as 9:30 PM.

Workaround

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