Saw this today and seems like something changed. The fixversion view when the pop up occurs and you can edit the start and release date, is correct. But when the fix versions are all seen in a list, the start and release dates are 1 day older and not correct.

Please fix this asap. This is regression.

@kkaczmarczyk@atlassian.com can this ticket please be cloned and reopened as this issue has been reintroduced into the latest cloud version.  Thank you!!

Hi.. We are still facing the issue, Can you let us know  when  are you going to fix things to the  Releases/Fix Versions in Jira?

Started happening today.

For customers experiencing this bug, please watch the following bug report instead:

• https://jira.atlassian.com/browse/JSWCLOUD-26565

This is happening to us also.

This is affecting our Jira Cloud instance as well. First report received today.

We had this issue on Data Center and once we migrated to Cloud in November we didn't have it anymore. Now I just confirmed it's a problem on Cloud for us too. 

Confirming this issue has started occurring on our cloud instance recently as well. This should be reopened or a new ticket created to address the regression. Thanks!

This issue just started affecting our Jira Cloud instance today.

We have reports of this problem on some Cloud projects. Should we be reporting this as an issue?

I've been using Jira for years and this just started affecting me today.  Why is this ticket closed?

If this is happening for us, should I submit a support ticket?

We experienced this issue recently. Another Jira admin resolved this by changing the Jira System Time to “GMT 4 (America/New York)” via System>General Configuration>Time Zone. I checked this setting also, and 'thought' it was set to this, but I could have overlooked it. However, after our other Jira admin noted it had been updated, I reviewed a few different projects' Releases that were appearing incorrectly, and confirmed they were now appearing with the right dates in both the main Releases list view, and when you clicked inside the Releases looking at the right-hand pane. It may be helpful to try 're-saving' the time to fix this?

Hello,

• Issue on the Release Page
• Our Jira account timezone is New York/EST (GMT -04:00) & my location timezone is also EST

My team is just now noticing this issue; this is a new issue for us.  When we were creating/closing out releases two weeks ago (May 5th), this was not a problem.  Now upon modification to the date field, for new or editing a release version, the date always changes to one day earlier than the one we selected.  The date has also changed to one day prior for all released versions prior to this two weeks.

Hi MJ

• Where: Release page
• Time zones: PST, Ireland Standard Time, etc.

When we modify the date field for a release, whether that's creating a new one or editing an existing one, the date is always one day earlier than the one we submit.

Hi Everyone,

My name is MJ Kim who is developer and works with Matthew Erickson. I appreciate if you could specify the timezone you are seeing this issue, and where you are seeing this(Backlog version panel/Version details page/Release page/If version modal, which modal), then it would be helpful to investigate further and fix it.

Thank you in advance.

We are still seeing this issue.

I am still seeing this issue.

Hi Everyone,

My name is Matthew Erickson, I am an engineering manager at Atlassian. Our team has recently made several fixes which we hope have solved this problem. As timezone issues are notoriously tricky I'm going to leave this issue open for a while longer. Please comment on this ticket if you think you are still seeing this issue.

this is a big issue, most of other tools manage the data conversion without issues, but Jira after all these versions still having this problem is not a good PR

I just started using the Roadmap view, which is great so far, except for this annoying date issue! I have to "fudge" Epic end dates so that the roadmap doesn't complain that the Epic ends after the Release date.

I would also like to see this issue fixed, as I have to explain to stakeholders that we are not actually off schedule by a day, but that Jira (which they already dislike) has a display bug.

Hi - is there an update on this issue?

Hi Atlassian team - this bug was opened in 2017 and it is still gathering impact?

Yes, this does impact our teams.

Can you please provide an update as to when this will be fixed? Any workaround? Thanks!

Any updates?

This is the longest in progress ticket I've ever seen. Jira is horrible at completing their tickets and correcting issues that are painful to their users (not specifically this casse, but more just a general statement).

Any progress on this?

Count yourself lucky that you get to be on UTC for a few months, and spare a thought for those of us on GMT+12
I mistakenly thought that if I created a release close to midnight (one side or other), or maybe close to midday, near the UTC day rollover, Jira might put in the right date. Sadly I don't think I've ever seen it do the right thing.

Just posting to say that the progress is so disappointing… but hey, we’re switching to winter time soon, so British time will be equal to UTC, so the bug will disappear for me until next March.

In the meantime, I have to pick the release date as “tomorrow” for a release happening today. Not what one expect to do, terrible workarounds for something so basic.

Today's release from the Kanban board (13 October):

and shown immediately after on the Releases page (12 October):

I'll post again after winter time has kicked in, just to show it's fixed! At least it buys Atlassian another 6 months of doing nothing, until next March.

No change nor update as of 11 June 2020. Below what I got by email with Atlassian last month and the month before.

Thread:  JST-521948 Still affected by JRACLOUD-67487

Update on 28 April 2020:

I just wanted to update you, I have spoken directly with the developer on:

• JRACLOUD-67487: Versions showing start date and release date 1 day earlier

He informed that this bug has been progressed by his team as far as can be, the last piece of work is indeed the Kanban board as detailed here:

• JSWCLOUD-18526: Incorrect date in the release page for new releases created directly from Kanban board

This is why no update has been placed on this bug for a while. Now I have raised a case internally to chase the progress of JSWCLOUD-18526 so please bear with me while I chase this and try and get an update for you. 

Update on 18 May 2020:

I just wanted to drop a courtesy update to let you know I am in talks with engineering about updates on https://jira.atlassian.com/browse/JSWCLOUD-18526 [...] I will let you know as soon as I have more info.

This problem had disappeared all winter (uk winter time = UTC), and it re-appeared for me at the end of March with the switch to summer time (British Summer Time BST = UTC+1). As mentioned in previous posts.

Linked ticket https://jira.atlassian.com/browse/JSWCLOUD-18526 was marked as “short term backlog” 5 months ago and no change since.

This ticket was marked “In progress” on 26 June 2018 and not updated since.

Ironically, it takes so long for this issue to be fixed that we can go through several winter and summer time changes to verify.

One can pick the next day and make it work. Example: Pick Jan 6 2020 if you want your release date as Jan 5 2020.

@kKaczmarczyk Watching & waiting for resolution

Nero in the support followed through with this one, offered to share screen, etc and eventually reproduced my problem on 25 Oct: 

So some good new I was able to replicate your issue. I also now know where the confusion came with me being unable to replicate originally.

The steps I was taking:

1. Create a release in the release page.
2. Assign the release to the Fix version field in the issue.
3. Move the issues with the assigned version/release to the done status in the board.
4. Select release and choose the existing version.
5. This then prompts to enter a release date.
6. Confirm the release and this then retains the correct date in the released versions on the releases page.

The steps to encounter your bug are:

1. Create issues in board.
2. Move issues to done status.
3. Click release and select New Version.
4. Create the version name and select the release date, then save.,
5. Review in the release page and indeed the date is one day prior to the data set when creating the release.

As such I have created a new bug to better report the specifics of the problem you are encountering and linked it to the existing one to maintain continuity:
https://jira.atlassian.com/browse/JSWCLOUD-18526

and then another update on 28 Oct:

I have spoken with my colleagues who first brought your comment on the bug which prompted me to create this ticket for you and they have confirmed the new bug and are working to expedite this with our product teams.

There is hope. Got this today, and replied with the same details as I had provided previously. This time it's got a ticket number: JST-521948. 

From: Nero Wolfgang 
Sent: 18 October 2019 10:46
Subject: JST-521948 Still affected by JRACLOUD-67487

Nero Wolfgang commented:

Hello,

My name is Nero Wolfgang, and I raised this case for your in response to your comment on JRACLOUD-67487

If I understand correctly from your comment this bug is still affecting you despite our changes in cloud which we believe addressed this issue. So we can see and undferstand exactly what is still happening in you case would you be able to provide me with some specific examples of projects and version where the data in the board view is incorrect?

One I have this In will start looking into this for you straight away.

Best Regards,
Nero Wolfgang
Senior Cloud Support Engineer | Amsterdam

Shame I've not managed to dedicate time to find an alternative to Jira.

Same issue is still here, no fix from the Jira team.

I got an email on 5 June 2019 from Atlassian which I hope was a sign it will be fixed:

From: Aman Batra 
Sent: 05 June 2019 14:35
To: Thierry Suzanne
Subject: Reg your Jira issue for incorrect release date

Hello Thierry,

Hope you are doing well.

I am a part of Jira cloud product management team at Atlassian. I came across the issue you are still facing with Jira (https://jira.atlassian.com/browse/JRACLOUD-67487).

We believe we have fixed this issue. However, I apologize that you are still facing it. It would be great if you could share some more information about the recent incident when it started happening for you again, like timezone (in Jira settings   and your profile settings in Atlassian site), what exact operation you performed in Jira, and your browser information.

Thanks,

Aman

I replied to say it was not fixed. Provided screenshots and details AGAIN.

This is still NOT FIXED. Every time I release from the Kanban board the release date changes to 1 day earlier, I must go to the Release page and Edit it, and change the date to today.

We are October 2nd, 2019. Issue raised on September 2017. Marked "In Progress" in June 2018 = 2 years of inaction.

Hi, I can confirm that the bug is back for me. It seems that it was fixed for the last few months for me. Coincidence or not, the UK has now switched to daylight saving (UTC+1). This morning 15 April, at 9:23 local time (a few minutes ago), I created a release from our Kanban board. Then going to the Releases page, it's listed with date 14 April.

This was raised in Sep 17, been in progress since June 2018, and still not fixed. One year and a half on. I've really had enough of Atlassian's poor support and am now looking for other ticket logging systems.

Could it be that it's fixed for me because i'm in winter time (no daylight saving) therefore GMT/UTC right now? Wait till March, when my time will shift by 1 hour ahead of GMT (daylight savings), maybe the issue will come back. I will report back here.

Still not fixed in our cloud instance either. 

I am using Jira Cloud and i still have this problem. Can you let me know what you did, to get this working on your end? 

Thanks!

For me, this is now fixed on Jira Cloud. Maybe due to the fixed related or duplicate tickets.

@Kamil Kaczmarczyk sorry it's not fixed (and sorry it took so long to get back to you).

Whatever date I put on the Release popup from the Kanban board, it still shows as a day earlier in the Release page (see picture).

[loosing the will to live: can't add attachement, can't drag+drop... so forget the attachement]

Quick update!

The release widget (both in Confluence and Jira dashboard) should now display proper start and release dates. Please let me know if that's not the case for you

thierry.suzanne the existing data will not be affected - in every place the date would be displayed as it is on Versions/Releases page.

ewuch there is no concept of release "time" in Jira, however since the date is stored as a "datetime" field type it is (or rather used to be) susceptible to timezone operations.

Please don't forget Jira Server and Portfolio in all of this. 

Kamil - how does a date have a timezone at all? That's more appropriate for a "datetime". Should the UI be rendering not just a date for this field but also a time of day? I've never seen such a thing nor been able to set it...

Good news it's being looked at, thanks.

How is existing data affected?

One comment above calls it a "display" issue, ie, it's stored in the DB as entered by the user, which would mean nothing to change at our end after the fix.

But if the value in the DB itself was stored with -1day, do we have to go back into Releases and re-adjust all our dates after the fix?

Thanks.

Quick update:

• This is a long running issue that was attempted to be fixed few times. Unfortunately, those attempts addressed a problem in some parts of Jira but not all of them
• In order to fix it properly once and for all we decided to store version’s release & start dates in UTC timezone, and avoid any timezone specific conversions
• Since making that change the following Jira pages were fixed:
  • Versions/Releases page
  • Release Hub

There are few more places pending updates:

• Release widget in Confluence
• Version view on Board Backlog

The fixes for those pages are planned for the coming weeks . I'll keep you updated on the progress.

9 months on, no fix.

Maybe Atlassian are busy preparing a new optional pay-for add-on for releases. Not really a core part of a ticket system is it, dating releases accurately? (sarcastic)

That's what they did after all when removing the widget to sum developers logged work time. Not part of core product, is it, summing up time? go buy a time management add-on instead!

Example from the new UI - issue still present...

What the admin enters when creating a release:

What the "users" see when viewing releases...the dates are not aligned

Since Last weeks Jira update of the Release summary screen, the date displayed on the summary list is one day behind the actual date for release.

What we are now seeing:

• Edit the version pop up - Release date in edit screen is correct Ex: 06/22 mm/dd
• Jira Issues Calendar widget - has the correct release date Ex: 06/22 mm/dd
• The Releases summary list page - shows one day behind the actual date Ex: 06/21 mm/dd

Only I go into the edit so the rest of my team has to rely on the summary list page or the calendar which now do not match. This is creating confusion and needs to be fixed.

Note Our time zone is (GMT-05:00) New York.

Had been seeing this "1 day early" behavior for a while in the Roadmap widget but now it's also showing up in the project's list of releases.  It's really confusing that the date in the "edit release" dialog is a day later than the date in the table of releases on the same page. 

In case it is relevant both the default user timezone and my profile timezone are set to (GMT-05:00) New York.

Agreed. This problem has been around for a long time, but it is much more visible in the new UI. 

Given the duplicate ticket: https://jira.atlassian.com/browse/JSWCLOUD-12880 (created in 2015) is associated with this ticket, it would seem that Atlassian has has left this problem as "unaddressed" since 2015?  Not a great response time.

I don't know how closely Atlassian watches this "voting." If all the folks "watching" this "voted" their preference / issue importance, then this ticket should "trend" for their attention and re-prioritization?  This issue seems important to more than one organization using the cloud.

Executives are continuing to wonder why the roadmap gadget is always off by one day.  This gadget is a key information point for our entire company – meant to be the single point of truth...not helping the product's credibility, just sayin'...