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

JAVA 8 in JIRA does not recognize some dates set in foreign language

XMLWordPrintable

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Summary of bug

      When using JIRA with JAVA 1.8 (and using it in a non-English language), JIRA might not recognize the dates properly, even when they are set according to the date picker format

      Steps to replicate

      1. Setup JIRA with JAVA 1.8 (preferable JIRA 6.3 and above)
      2. Set JIRA to use one of the affected languages (more on that later). For now we shall use German
      3. Set the due date to be in March
      4. The result is as follows :

      Additional Info

      • This does not seem to be able to be replicated if using JAVA 1.7 or below
      • Another affected language found so far is Czech :
      • This seems to only affect certain months/patterns (for example, using the German language example above, March is affected, but not December)
      • Tested in JIRA 6.3.9 with Postgres

      Possible Workaround:

      • Change the date format from 20/Mrz/15 to 20.03.15 with the below setting in Advanced Settings: 
        jira.date.picker.javascript.format=%d.%m.%y
jira.date.time.picker.javascript.format=%d.%m.%y %H:%M
jira.date.time.picker.java.format=d.MM.yy H:mm
jira.date.picker.java.format=d.MM.yy

        1. czech lang.png
          czech lang.png
          57 kB
        2. german lang.png
          german lang.png
          57 kB

            [JRASERVER-41321] JAVA 8 in JIRA does not recognize some dates set in foreign language

            Mohamed Lee added a comment - - edited

            not fixed in v7.13.8, but the workaround still works

            Mohamed Lee added a comment - - edited not fixed in v7.13.8, but the workaround still works

            Jens Kisters [APTIS] added a comment -

            Hey everbody,

            i doubt Atlassian will react on comments on a resolved bug,

            i recommend to raise a new bug or find the recent version of this bug.

            In the meantime use the workaround described.

            kind regards

            Jens

            Jens Kisters [APTIS] added a comment - Hey everbody, i doubt Atlassian will react on comments on a resolved bug, i recommend to raise a new bug or find the recent version of this bug. In the meantime use the workaround described. kind regards Jens

            Anne added a comment -

            Here is another workaround for the German local version: The value of the field can be modified manually into "14/Mär/17" (instead of "14/Mrz/17"). Then the input works. Anyway still annoying...

            Anne added a comment - Here is another workaround for the German local version: The value of the field can be modified manually into "14/Mär/17" (instead of "14/Mrz/17"). Then the input works. Anyway still annoying...

            Stephan Fürnrohr added a comment -

            Same here, Atlassian Cloud JIRA for German locale seems to be broken. We can't do any planning for March - please fix this ASAP.

            Stephan Fürnrohr added a comment - Same here, Atlassian Cloud JIRA for German locale seems to be broken. We can't do any planning for March - please fix this ASAP.

            Hannes Geist added a comment -

            Can confirm this, can be reproduced in current Atlassian Cloud JIRA for German locale. Unacceptable, please fix soon. (It will soon be March, customer already has problems planning his work).

            Hannes Geist added a comment - Can confirm this, can be reproduced in current Atlassian Cloud JIRA for German locale. Unacceptable, please fix soon. (It will soon be March, customer already has problems planning his work).

            Andreas Ebert added a comment - - edited

            Fyi, in my JIRA 7.3.0 this also occurs again.

            And I predict that coming this March more people will be affected by this bug.

            Andreas Ebert added a comment - - edited Fyi, in my JIRA 7.3.0 this also occurs again. And I predict that coming this March more people will be affected by this bug.

            Oswaldo Hernandez (Inactive) added a comment -

            Hi francisco.silva,

            Could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and keep your confidential information restricted to just you and our support team. The credentials should be the same as for this site (https://jira.atlassian.com).

            Regards,

            Oswaldo Hernández.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi francisco.silva , Could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and keep your confidential information restricted to just you and our support team. The credentials should be the same as for this site ( https://jira.atlassian.com ). Regards, Oswaldo Hernández. [Atlassian] .

            FRANCISCO SILVA added a comment - - edited

            Hi Sebastian!

            I have tha same version and the same problems!

            Did you have a solution for this?

            FRANCISCO SILVA added a comment - - edited Hi Sebastian! I have tha same version and the same problems! Did you have a solution for this?

            Deleted Account (Inactive) added a comment -

            Hello,

            we are using JIRA 7.1.7 and the issue still occurs.

            Cheers,
            Sebastian

            Deleted Account (Inactive) added a comment - Hello, we are using JIRA 7.1.7 and the issue still occurs. Cheers, Sebastian

            varcess added a comment -

            Hello,

            I have changed the advanced settings to the date format 17.03.2015 and now everything works fine.

            Thanks for advice.

            Best regards
            Daniel

            varcess added a comment - Hello, I have changed the advanced settings to the date format 17.03.2015 and now everything works fine. Thanks for advice. Best regards Daniel

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              jtye Joe Wai Tye (Inactive)
              Affected customers:
              21 This affects my team
              Watchers:
              46 Start watching this issue

                Created:
                Updated:
                Resolved: