Incorrect Version Release Date on Jira Project Release page

[Ron Jacob]

Hi 

In Jira Project

On Manage Versions page - Release date is correct  3/20/2018

On Release page - Release date is incorrect  3/19/2018

[Andy Heinzer]

Hi Ron,

I have seen this happen before, but it tends to be because of a difference in timezones.   When a release date is set in Jira, it only shows you a date.  But when Jira is storing that value in the database, it's using a date and time value.  This value for time tends to be exactly 0:00 (or midnight).

This tends to work just fine in environments where the timezone of the Jira Server is exactly the same with all the users.  However if your user profile timezone is behind the Jira server timezone by even 1 hour or more, then the release date will appear to be the day before for you.

There is a documented bug on this in https://jira.atlassian.com/browse/JSWSERVER-12880

That bug ticket suggests that you set the timezone in the Jira administration menu to match the timezone in use via the Java start up parameters in https://confluence.atlassian.com/jira064/choosing-a-time-zone-720416101.html

[April]

Hi Andrew,

I added -Duser.timezone=America/New_York to Java, as my server is in (UTC-05:00) Eastern Time (US & Canada). This fixes the appearance of release date in most views, BUT.. To display Release Date and other date fields on issues, I have to use ScriptRunner, which is affected by the one hour off problem you describe.

How hard would it be for Jira to use only date without the timestamp for values like this where the exact time is irrelevant?

Thanks.