Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-29088

Time zone contradicts on Date Picker field with Google Chrome

      When click on Date Picker custom filed on an issue screen, the time contradicts with the original server time zone and also with the user's preferred time zone. This behavior appears only with Google Chrome. Tested on JIRA 4.4.4, 4.4.5 and 5.0.

      Screenshot attached

            [JRASERVER-29088] Time zone contradicts on Date Picker field with Google Chrome

            Hi mmarkc,

            There is no known workaround, so the only solution at the moment is to upgrade your JIRA instance.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi mmarkc , There is no known workaround, so the only solution at the moment is to upgrade your JIRA instance. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            luc.vandenboomgaerde,

            The JIRA bugfix does not provide patches for bugs in older versions of the product. All bugfixes are delivered in the next maintenance for the latest stable release in JIRA.

            Consequently, it will be necessary to perform an upgrade if you are interested in obtaining this fix. For more information, please consult https://confluence.atlassian.com/display/Support/Atlassian+Patch+Policy

            Also, I will remove the sub-task you have created under this issue, if you need to ask a question about any other JIRA bug in the future you can add a comment on the issue and we will get back to you.

            Hope this helps.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - luc.vandenboomgaerde , The JIRA bugfix does not provide patches for bugs in older versions of the product. All bugfixes are delivered in the next maintenance for the latest stable release in JIRA. Consequently, it will be necessary to perform an upgrade if you are interested in obtaining this fix. For more information, please consult https://confluence.atlassian.com/display/Support/Atlassian+Patch+Policy Also, I will remove the sub-task you have created under this issue, if you need to ask a question about any other JIRA bug in the future you can add a comment on the issue and we will get back to you. Hope this helps. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Has anyone found a workaround for this problem? We can't simply upgrade to JIRA 6.

            Mark Claydon added a comment - Has anyone found a workaround for this problem? We can't simply upgrade to JIRA 6.

            HI rgarciape,

            This issue looks like a duplicate of JRA-26265 which was fixed in JIRA 6.0.3.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - HI rgarciape , This issue looks like a duplicate of JRA-26265 which was fixed in JIRA 6.0.3. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Raúl García Pérez added a comment - - edited

            Is this issue resolved?. For version 5.2 of JIRA the problem is reproduced in Chrome.

            Raúl García Pérez added a comment - - edited Is this issue resolved?. For version 5.2 of JIRA the problem is reproduced in Chrome.

            Can someone of Atlassian look into this?
            It makes it difficult to use Chrome for JIRA

            Dieter Greiner added a comment - Can someone of Atlassian look into this? It makes it difficult to use Chrome for JIRA

            It seems JRA-26693 specifies the same behavior and it include IE9

            Florin Haszler (Alten Kepler) added a comment - It seems JRA-26693 specifies the same behavior and it include IE9

              Unassigned Unassigned
              skhanam Shapla Khanam [Atlassian]
              Affected customers:
              4 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: