-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
2.18.0, 2.27.0, 3.6.0
-
None
-
33
-
Severity 3 - Minor
-
0
-
Summary
Target start/end fields are stored incorrectly on the Issue history.
Environment
- user.timezone set to any "western" timezone (eg. America/Sao_Paulo)
Steps to Reproduce
- Set a Target end value
- Verify Issue history
Expected Results
Issue history displays the same value specified
Actual Results
Issue history displays the day before the date specified
Solution / Workaround
- Set system user timezone to UTC at Jira JVM properties
-Duser.timezone=Etc/UTC
Note that different user and system timezones can result in the behavior described in
JRASERVER-41646
- Restart Jira
- duplicates
-
JSWSERVER-21994 Target Start and Target End custom fields behave as though they were a day behind when system timezone is set to negative offsets
-
- Closed
-
-
JPOSERVER-2358 Bug: Target Start and Target End fields store incorrect values in CEST within jira create rest calls
-
- Closed
-
- is blocked by
-
JRASERVER-41646 Releasing a version shows the Release Date one day behind the date originally set
-
- Closed
-
- is related to
-
CONFSERVER-98215 Due date shows one day behind in confluence when timezone is set to PST timezone
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Dear all,
I would like to inform you that the Jira DC Development team has reviewed the following issues: JSWSERVER-21994 and JPOSERVER-2459. After careful consideration, we have determined that they describe the same issue. Therefore, all issues will be merged into JSWSERVER-21994, while the other issues will be closed. If you would like to keep track of the problem, please vote and watch JSWSERVER-21994.
Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Daniel Dudziak
Jira DC Senior Software Engineer