-
Bug
-
Resolution: Unresolved
-
Highest
-
None
-
10.0.0, 9.7.0, 9.7.1, 9.11.2, 9.4.14, 8.20.30, 9.17.0, 9.12.12, 9.4.23, 9.12.10, 9.12.11, 9.12.15
-
8.2
-
37
-
Severity 2 - Major
-
105
-
Issue Summary
This is reproducible on Data Center: Yes
Steps to Reproduce
Scenario 1
- Install Jira with Microsoft SQL as the database
- Navigate to Administration » System » General Configuration and set the System Timezone to America / Chicago
- Set your user's timezone to Chicago
- Add a version with a release date to a project.
- Change profile time zone to New York and check on the release to see it is now a day behind
Scenario 2
- Install Jira with PostgreSQL as the database
- Navigate to Administration » System » General Configuration and set the System Timezone to GMT OffSet and choose "GMT-7"
- Add a version with a release date to a project.
- The release date is behind 1 day.
- Changing the user profile to the same as the System Timezone. The release date still behind 1 day. Also, it does not honour the user profile timezone changes.
Expected Results
Release dates do not change when changing profile
Actual Results
The date changes to the day prior
Workaround
Scenario 1:
- Set the timezone of every user to match the Jira default
Scenario2:
- Set the Default user time zone back to the System Default timezone (the same timezone matching with the jvm.system.timezone ) via Administration > General Configuration > Edit settings.
You can find the timezone for "jvm.system.timezone" via Administration > System Info.
- causes
-
JIRAAUTOSERVER-1097 When copying a value stored from release/fixversion the copied date is one day behind
-
- Gathering Impact
-
- derived from
-
JRASERVER-41646 Releasing a version shows the Release Date one day behind the date originally set
-
- Closed
-
- is related to
-
JRASERVER-75894 Invalid format error when building and releasing a version
-
- Closed
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...