So this isn't really fixed if there is a new bug to track now???  Please explain how this makes sense.

Everybody, all the Watchers - it would be good if you voted for the new bug that is in Gathering Impact status

• JRASERVER-76438 Release versions show the Release Date one day behind the date originally set

https://jira.atlassian.com/browse/JRASERVER-76438

New bug to track this on going issue

We have this issue in our Jira Data Center Instance (v8.20.10#820010)

Still seeing this issue in Jira 8.20.10

This issue appears to still be unresolved in Jira 9.7.0.

System Time: Australia/Sydney (GMT+10)
User Time: Chicago (GMT-6)

Additionally, issue occurs even if System Time and User Time are the same (GMT-6)

Does this fix also fix the Cloud version issues? I see attached JRACLOUD-41646 issue is closed/fixed but date shows 2017.

To confirm, this fix is now available in version 9.7.0?

We would like to see this get fixed at some point in the long term as it messes with our reporting on releases

Any new updates to the progress of this?? This affects all versions that I am aware of, not just the versions listed above.  I know it affects version 9.1.0

To be honest, as Jira and Confluence admin, this is a giant issue, a critical bug, this is a big, huge shame on you. 

Hi b77f0901d138 - Just wanted to confirm that 8.20.10 (LTS) is in the affected version list. 

Cheers, 
J van Leeuwen | Atlassian Principal Support Engineer  

This also impacts 8.20.10 (LTS) - I see Leonardo Souto recently updated this to show it impacts 8.19, but I can't seem to tag him so I hope he can update.  The "Affects version" list is so long it doesn't show in the interface.

@joe harmon - Jira Data center is not discontinued and if you look at the top left this project is for Jira Server and Data Center, so Data Center customers can have hope, although I don't have a lot just based on the Atlassian track record for fixing bugs. 

I obviously can't speak for Atlassian, but I wouldn't get your hopes up for this being fixed.  They have announced the end of support for Jira server.  If they didn't fix it before the end of support, do you really think they are going to fix it now?  Plus Atlassian is notorious for not answering.

Yes, this needs to be pri'ed and fixed. It's annoying to ask stakeholders to look at the release train and explain to them that the date is a persistent know issue that Atlassian doesn't want to fix. Doesn't really inspire confidence if your team's adoption of an Agile PM tool that can't even display dates correctly.

Can we prioritrize this as its blocking our engineering teams ?

This bug was highlighted during a recent migration effort and created confusion for a sample of our users.  While we do appreciate the transparency of your approach, our appreciation would be increased orders of magnitude by a fix   Hopefully Atlassian will consider revisiting this topic 

Our teams are also blocked by this. Can you please prioritize this bug fix? Thanks.

What's the timeline to fix this? How can we help?

I am managing contract end dates using Jira so a one-day error is really bad for us. How do I vote on a topic? Thanks

We would appreciate this be escalated so that we can utilize reporting and communications on Implementations more effectively as it is this makes Jira more or less just a task tracking tool.

This "Major" severity issue is now over seven years old. To quote a famous-but-fictional railroad controller, it is causing "confusion and delay" in our organization. Please do right by your customers and fix it ASAP. Thank you.

This is causing a lot of issues for us lately and sporadically over the years. Somehow lately more complaints though. Hope it gets more votes before more people start thinking they are bonkers when they see the dates change on them for no reason they can identify.

Agree with Julie. Please make this a higher priority to fix. Large companies are developing workarounds to account for this inconvenience. 

This is still greatly needed.  No updates since June of 2019? Unacceptable.  Please look into making this a higher priority. 

> We would not be able to address the release date case independently, yet addressing the problem completely in the product would require a significant investment.

I don't really see it as a huge investment - a simple enough change would be going forward to allow picking a date and time, with the time defaulted to midday. Using midday rather than midnight would mitigate these problems when the user is in a timezone west of the server timezone. 

Currently the internal structure that represents the release/start date is a java Date, which is effectively an instant in time, and the db column is a timestamp. Therefore the existing API and database already supports this. And this change would only affect the defaults going forward, so I'm surprised it's viewed as a big change.

NB - this affects us via https://productsupport.adaptavist.com/browse/SRJIRA-5278. 

Tried the workaround here:  https://jira.atlassian.com/browse/JSWSERVER-12880

Could then at least fix the dates even though they saved wrong which is how it was working for us before we upgraded from 7.0.11 to 8.13.4 recently.  Even though they initially saved wrong you could manually fix them and then they'd stick.  However, after applying the workaround the Activity Stream timestamps and timestamps in JIRA issues were then wrong.  Had to revert the workaround suggestion.

I hope this ticket will gain some traction at some point. Not being able to date things correctly in boards and projects is very frustrating and confusing to users.

Are you on an AWS instance for your server?  If so, where does your server physically reside?  And what is the Jira default timezone set to?

In our instance, the server/JVM are set "ZONE=America/New_York".  And I am in EST.  Still the date shows as one day earlier in the popup dialog when performing the "Release" operation.

This is a self-hosted Jira Data Center instance located in the company's east coast data center.

Default user time zone = System default: (GMT-05:00) New York

Our IT set it for us.  We are using AWS servers so they had to match the location of the AWS server.  It is the JVM time zone.  It should match your time zone for the server itself.  In this case your Jira default time zone and JVM time zone should match as far as I remember.  The local time zone will adjust accordingly.  You time is probably off the difference between the JVM and Jira default time zone.

Hi @joe Harmon

Curious if you know which setting on the JVM we need to set.

my system is set to Australia/Sydney but seeing different settings within the JVM.  

user.timezone : Australia/Sydney
jvm.system.timezone : America/California
jira.default.timezone : America/New_Jersey

You can resolve it yourself on Jira server.  Go on the server in question and set the JVM timezone.

Can we get confirmation if this bug will be resolved on Jira server?

Is there any update on this ? 
When setting up a version with Release Date of for example 9th dec on my test project , its changing the release date to 1 day prior to that which I set
 
I dont see this buf on Jira cloud side. 
 
Thanks, 
Faisal

I did a release yesterday and the problem is gone at my side (cloud version). I believe they introduced a new date picker  

I doubt they will fix it for Jira Server since they announced it was going end of life a few years from now.

Me too Steph S. What is inconceivable is how Atlassian invests in new features but can't dedicate resources to fix an issue like this. I hope that we get some update before the 6th anniversary of this bug.

Yes, exactly. This seems like it should be an easy fix. I'm not sure why it's still lingering.

I agree with this comment:

https://jira.atlassian.com/browse/JRASERVER-41646?focusedCommentId=2487401&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2487401

A quick fix... this issue was created on 15/Jan/2015. LOL

This seems like it should be a very quick and easy fix. Could you please prioritize this? Thanks.

_

Also, if you go to edit mode, it will load the dates that are are 1 day off. Then, if you save them again, they will be two days off. Very confusing.

How is this not a high priority bug? 5 Years? this is ridiculous. 

This issue definitely impacts my team and makes our customer, the U.S. Government, less confident in our planning efforts (and more importantly our decision to use Atlassian products for SW development). This has been going on for FIVE years? Very disappointing...

How do I unsubscribe from this thread? I'm not listed as a watcher but I still get emails for every new comment added. 

This seems like a priority for engineering teams as it is how we communicate when we are releasing to our business stakeholders. I think if you are placing yourself in a space where you are the primary communication tool on developing and releasing this is a MMP.

I'm really disappointed that Atlassian have been "gathering impact" of this issue for nearly 5 years now with no commitment to resolution and countless comments and upvotes.

This is an issue that really affects my team's workflow and is incredibly frustrating.

If Atlassian can't commit to further work on this issue, I may be forced to reconsider my use of Jira going forward.

User in our system defines several releases, and the dates are no problem - the dates he chooses are displayed.  Then, all of a sudden the release date he last enters resets itself back a day for both start and finish.  Jira 8.3.4.  I've tried editing the dates, and Jira allows me to enter the dates, but then they display on the Releases window as -1d  than what I set.