Solution: Stop stripping the time from date string. Jira is stripping the time from the ISO 8601 format and treating it as midnight in the Jira default time zone resulting in this bug.

An example is an EST time zone default Jira server where other users may be in the CST time zone. Since CST is 1 hour behind EST and Jira strips the time and defaults to midnight in the default time zone, it then results in the previous day at 11PM for CST users.

I've provided the technical cause and solution. All that has to be done is implementation.
Please fix immediately.

Sadly this has been an issue since at least 2015 and still not resolved. I'm not sure why this is Gathering Impact when it's been happening for a long time now. It was supposedly fixed in JRASERVER-41646 Releasing a version shows the Release Date one day behind the date originally set - Create and track feature requests for Atlassian products. but apparently not??

PLEASE FIX THIS! You KNOW it impacts everyone!

I wish it would just save the date when I click the button that says "perform release." There are other timestamps in jira (like last updated date). If we did that, then the dynamic date would be fine, because if we really did release at midnight eastern time, the local date in Arizona would be correct even if it was off by a calendar day.
 
 
Another option is, just like sprint start dates, let me manipulate the hh:mm so that I can set it on behalf of my team to represent a moment in time.

This is a big deal for us. It is sad to find that this bug is not fixed yet. Our team spread across US and date difference causing the confusion. East to west US timing is just 3 hours difference but not a day (24 hours) difference. May I know when this can be fixed? 

We have team members across time zones, and this issue is impacting our ability to leverage automated deployment tooling, schedule multi-team deployments, and track/troubleshoot production issues due to deployments.  Futher, Jira itself does not seem to track and recognize my time zone consistently at different points in the application.

Our teams are encountering this issue, too, and one of the more frustrating parts is that it becomes hard to discern what the real date of the release is when different people see different dates (and even see different dates in different views). 

For us, one of our users had profile settings set to "Dublin" and was seeing release date June 24 in the version configuration but release date June 23 on dashboards. For other users, they saw June 23 in both the version configuration and the dashboard.

This is a localization problem and again, makes it difficult for teams to identify what date is accurate without checking everyone's personal time zone settings.

This affects my team on version 9.12.8

Dear devs, this issue affects my team, please take this into work, thanks in advance!

Also finding this is affecting Jira Automation. I should be able to use a Smart Value in an Automation Rule to pull one of the dates on a Release and use that date effectively in the Rule.

However, some odd timezone thing is in play. Server and User timezones on our Data Center version are identical (US/Chicago) for the test illustrated below:

(thanks so much for not letting me paste a screenshot, as an authenticated user)

My test set the "Release Date" for a Version to be "15/Dec/23" (aka 15-Dec-2023). The following Smart Value results were observed when reading and formatting that value in an Automation Rule:

• issue.fixVersions.first.releaseDate.format("yyyy-MM-dd")
  2023-12-14

• issue.fixVersions.first.releaseDate.fullDateTime
  Thursday, December 14, 2023 6:00:00 PM CST

Workaround for this in Jira Automation:

issue.fixVersions.first.releaseDate.convertToTimeZone("UTC").fullDateTime

This is also affected on v9.12.3, when I try to Release a version its showing a day behind.

Steps to reproduce:

• Go to Jira project 
• Releases
• Add a test version / Edit any existing release.
• Set the release date with Current date on the Test version
• use 3 dots (...) click on Release button, it will pop a screen and in that you will see a Day behind on release date.

Thanks,

Phanidhar