Severity 3 - Minor
Thank you to everyone for your patience whilst we work on this issue. We can now confirm that this problem should be resolved for JIRA Cloud customers.
If you continue to experience this issue, or you are a customer experiencing this issue for the first time, please do get in touch with our Support team (getsupport.atlassian.com) to get the best assistance in remedying the problem.
JIRA Cloud team
When adding a value in the Due Date field, the user filled in the time expected in the timezone set in their profile. However, this date is converted to UTC and is perceived as the wrong date for the users of Jira.
This occurs for Due dates on issues, Start & Release dates on versions, and Date-only custom fields on issues (not Date&Time custom fields).
Currently there is no workaround
JRACLOUD-67326 Releasing a version shows the Release Date one day behind the date originally set in Cloud latest infrastructure
- relates to
JSWCLOUD-22316 Versions showing start date and release date 1 day earlier
- Gathering Impact
- is cloned by
- mentioned in