We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-26693

Initial time shown for date time custom field is not correct for the user's timezone in Chrome, IE9 and Safari.

XMLWordPrintable

      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".

        1. Screenshot-16.png
          Screenshot-16.png
          31 kB

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-26693

            Initial time shown for date time custom field is not correct for the user's timezone in Chrome, IE9 and Safari.

            XMLWordPrintable

                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".

                  1. Screenshot-16.png
                    Screenshot-16.png
                    31 kB

                        Unassigned Unassigned
                        mtan MinanA
                        Votes:
                        17 Vote for this issue
                        Watchers:
                        20 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            mtan MinanA
                            Affected customers:
                            17 This affects my team
                            Watchers:
                            20 Start watching this issue

                              Created:
                              Updated:
                              Resolved: