Loading...

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Target start/end fields are stored incorrectly on the Issue history.

Issue history displays the same value specified

Issue history displays the day before the date specified

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

JPOSERVER-2358 Bug: Target Start and Target End fields store incorrect values in CEST within jira create rest calls

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

is blocked by

JRASERVER-41646 Releasing a version shows the Release Date one day behind the date originally set

is related to

JRASERVER-73401 Due date shows one day behind in confluence when timezone is set to PST timezone

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...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(36 mentioned in, 2 relates to)