-
Bug
-
Resolution: Duplicate
-
Low (View bug fix roadmap)
-
4.4, 5.0, 5.0 - EAP, 5.1.3
-
None
-
4.04
-
When selecting a date for a custom date and time picker field, the initial time shown does not reflect the user's timezone preference in Chrome, IE9 or Safari correctly. To reproduce,
- add a custom date time picker field
- set the user's timezone to a non-zero offset
- create an issue in Chrome, and in Firefox for comparison
This was reproduced in Chrome 16.0.912.63 and Firefox 8.0.1.
Update: This was reproduced in Chrome 26, Safari 6.0.4 and IE9. Firefox 21 did not show this problem.
I suspect it to be caused by our parsing of ISO8601 date strings in JS. Because we don't append "Z" to the date string. The spec is ambigious on this (http://zetafleet.com/blog/javascript-dateparse-for-iso-8601) Chrome seems to interpret this as "client side offset", but Firefox as "no timezone offset".
- duplicates
-
JRASERVER-26265 Date Time custom field doesn't calculate current time
-
- Closed
-
- is duplicated by
-
JRASERVER-29088 Time zone contradicts on Date Picker field with Google Chrome
-
- Closed
-
-
JRASERVER-30107 Custom field of Date Time Picker is display local date time wrongly.
-
- Closed
-
- is related to
-
JRASERVER-27085 Date Time Picker are not following the server/profile setting time
-
- Closed
-
- relates to
-
JRASERVER-28904 Releasing a version with a pre-filled release date is giving an invalid date error for non-US clients
-
- Closed
-
Initial time shown for date time custom field is not correct for the user's timezone in Chrome, IE9 and Safari.
-
Bug
-
Resolution: Duplicate
-
Low
-
4.4, 5.0, 5.0 - EAP, 5.1.3
-
None
-
4.04
-
When selecting a date for a custom date and time picker field, the initial time shown does not reflect the user's timezone preference in Chrome, IE9 or Safari correctly. To reproduce,
- add a custom date time picker field
- set the user's timezone to a non-zero offset
- create an issue in Chrome, and in Firefox for comparison
This was reproduced in Chrome 16.0.912.63 and Firefox 8.0.1.
Update: This was reproduced in Chrome 26, Safari 6.0.4 and IE9. Firefox 21 did not show this problem.
I suspect it to be caused by our parsing of ISO8601 date strings in JS. Because we don't append "Z" to the date string. The spec is ambigious on this (http://zetafleet.com/blog/javascript-dateparse-for-iso-8601) Chrome seems to interpret this as "client side offset", but Firefox as "no timezone offset".
- duplicates
-
JRASERVER-26265 Date Time custom field doesn't calculate current time
-
- Closed
-
- is duplicated by
-
JRASERVER-29088 Time zone contradicts on Date Picker field with Google Chrome
-
- Closed
-
-
JRASERVER-30107 Custom field of Date Time Picker is display local date time wrongly.
-
- Closed
-
- is related to
-
JRASERVER-27085 Date Time Picker are not following the server/profile setting time
-
- Closed
-
- relates to
-
JRASERVER-28904 Releasing a version with a pre-filled release date is giving an invalid date error for non-US clients
-
- Closed
-