Date fields are showing one day behind the date originally set date when system timezone is Montevideo

Summary

First of all this issue is very similar to this one:
https://jira.atlassian.com/browse/JRA-41646

However, I wasn't able to tell whether they have the same root cause or not, as this refers to the different fields and timezones. If this is the case, feel free to close this bug as duplicate and we can update the other one.

When a user has an instance in timezone America/Montevideo, when setting a date, the actual date the user sees is one day behind.

This is likely caused by the Daylight Saving Time. This was replicated on November/25/2015 (not on DST).

This cannot be replicated by using the user's timezone in the profile page. This setting must be the system setting to cause this problem.

Steps to Reproduce

1. Have a JIRA Cloud instance with system timezone set to America/Montevideo
2. Create an issue
3. Set the due date for this issue

Expected Results

The due date displays the date the user entered.

Actual Results

The date is one day behind.

Notes

This is stored in the database for due date:

2015-11-27 00:00:00-02

If we convert to GMT-3, we get '2015-11-26 23:00:00-03', which explains why the previous day is displayed.

This bug may be related to this:
https://jira.atlassian.com/browse/JRA-45667

Workaround

None so far.