Cloud instances with timezones in Moscow are showing due dates with one day behind after setting them.

By checking the database, we can see that the dates are correct, they are only displayed incorrectly.

Steps to reproduce

1. Have a Cloud JIRA instance with system timezone in Moscow
   • It doesn't work with user timezone settings in profile, the system timezone must be Moscow
2. Create an issue
3. Set the timezone, for example to 12/31/2015

Expected behavior

• Due date displays the inputed date (12/31/2015)

Actual outcome

• It displays the date of the previous day (12/30/2015)

Workaround:
Raise a support ticket (support.atlassian.com) and ask to change the instance timezone from Moscow to another city GMT+3