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

JIRA doesn't recognize "Mrz" abbreviation for March in German

XMLWordPrintable

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

      Steps to reproduce:

      1. Go to General Configuration
      2. Change Indexing Language to German
      3. Change Default Language to Deutsch (Deutschland)
      4. Change Default user time zone to Europe and Timezone to (GMT+01:00) Berlin
      5. Change any date picker field (e. g Due Date) to any date in March (e.g 4/Mrz/15 10:25 PM)

      Expected Result:

      • JIRA should be able to recognize "Mrz" abbreviation for March

      Actual Result:

      • Error thrown as below:
      duedate: Sie haben kein gültiges Datum eingegeben. Geben Sie das Datum im Format 'd/MMM/yy' ein (z. B. '16/Dez/14').


      duedate: You did not enter a valid date. Please type the date in the format 'd / MMM / yy' (for. & Nbsp; B '16 / Dec / 14 '.).

      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. mrz.png
          mrz.png
          17 kB

          Form Name

            [JRASERVER-41268] JIRA doesn't recognize "Mrz" abbreviation for March in German

            it-service-frankfurt added a comment -

            Apparently not. Had to answer a support request by advising a user to temporarily switch from profile language German to English.

            it-service-frankfurt added a comment - Apparently not. Had to answer a support request by advising a user to temporarily switch from profile language German to English.

            Noel Krull added a comment -

            Is there already information for a fix?

            Noel Krull added a comment - Is there already information for a fix?

            Christian Loosli added a comment -

            You have got to be kidding me, how is this a "low" priority and not resolved yet?

            We can't create any new sprints without that workaround in our cloud instance, which we are paying money for.

            This is critical at least, and something that honestly should not happen in 2017 any more. Fix and deploy that quickly.

            Christian Loosli added a comment - You have got to be kidding me, how is this a "low" priority and not resolved yet? We can't create any new sprints without that workaround in our cloud instance, which we are paying money for. This is critical at least, and something that honestly should not happen in 2017 any more. Fix and deploy that quickly.

            Robby Beyer added a comment -

            Same here - contacted support, they have applied a work around and I have changed all Javascript Datetime-Picker Formats to dd.mm.yyyy. This will help. Anyway all comments should be made in the new bug here:

            https://jira.atlassian.com/browse/JRA-62769

            Robby Beyer added a comment - Same here - contacted support, they have applied a work around and I have changed all Javascript Datetime-Picker Formats to dd.mm.yyyy. This will help. Anyway all comments should be made in the new bug here: https://jira.atlassian.com/browse/JRA-62769

            Jörn Depenbrock added a comment -

            Push. same problem here. Atlassian Cloud.

            Jörn Depenbrock added a comment - Push. same problem here. Atlassian Cloud.

            Florian Kollin added a comment -

            We experience this problem with the local version of JIRA 7.20 Build Number 72002. 

            Thanks for the workaround Markus!

            Florian Kollin added a comment - We experience this problem with the local version of JIRA 7.20 Build Number 72002.  Thanks for the workaround Markus!

            Markus Troeszter added a comment - - edited

            Cant be that this bug aint going to be solved. THATS URGEND!
            Cloud JIRA Version is not working with german language, you have to manually type in "/mär/" instead of "/mrz/".
            Thats not a solution!

            Markus Troeszter added a comment - - edited Cant be that this bug aint going to be solved. THATS URGEND! Cloud JIRA Version is not working with german language, you have to manually type in "/mär/" instead of "/mrz/". Thats not a solution!

            Lars Fischer added a comment -

            Having the same problem here with a cloud hosted JIRA version.

            Lars Fischer added a comment - Having the same problem here with a cloud hosted JIRA version.

            Hannes Geist added a comment -

            Bump! Still not fixed. Unaccetable. You cant let this lay arround for two years for all German customers. I dont book cloud to then execute 10 workarrounds for 2 year old breaking bugs!

            Hannes Geist added a comment - Bump! Still not fixed. Unaccetable. You cant let this lay arround for two years for all German customers. I dont book cloud to then execute 10 workarrounds for 2 year old breaking bugs!

            Jörg Brunner added a comment -

            Sorry guys,

            this issue is still a problem for all JIRA-Users in Germany. I can not understand that it is still not fixed! We use JIRA Cloud so we have the actual Version.

             

            Jörg Brunner added a comment - Sorry guys, this issue is still a problem for all JIRA-Users in Germany. I can not understand that it is still not fixed! We use JIRA Cloud so we have the actual Version.  

              Unassigned Unassigned
              rsaputra Adven
              Affected customers:
              16 This affects my team
              Watchers:
              60 Start watching this issue

                Created:
                Updated:
                Resolved: