Details
-
Bug
-
Status: Closed (View Workflow)
-
Low
-
Resolution: Fixed
-
2.18.0, 2.27.0, 3.6.0
-
None
-
None
-
15
-
Severity 3 - Minor
-
35
-
Description
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
Attachments
Issue Links
- duplicates
-
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
-
- Gathering Impact
-
- mentioned in
-
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...