Atlassian Update on June 11th

      Hi everyone, thanks again for the interest on this ticket. We’re marking this ticket as closed now because a workaround has been released to solve the issue of "users always being forced into the American format of mm/dd/yyyy" by allowing each user to format their dates and times on the new issue view based on their language preferences. For many of you, this workaround solved the problem.

       

      Cross-post May 24th update on workaround

      • Users can now change the default edit and display of both date and date/time fields, using their language/locale setup (i.e. "en_AUS" or "Dutch") instead of being forced into the American month/day/year display only. Here’s how to setup yours: https://support.atlassian.com/atlassian-account/docs/manage-your-language-preferences/.
      • For those using language not supported (i.e. Greek). We suggest you choose UK English as your preference to get the desired display of day/month/year.

      For those customers that still face challenges with this solution we have opened a new ticket where we will gather interest specifically on when the user level language based settings is not a viable solution. Please comment on this new ticket https://jira.atlassian.com/browse/JRACLOUD-76814 to let us know your specific use case (i.e. why it’s important to have a specific date/time settings, and whether you’d like it at admin or user level), so we can ensure the experience we release works for you.

      For those concerned about their calendar locking Sunday as the first day of the week, watch and comment on this ticket: https://jira.atlassian.com/browse/JRACLOUD-71611 

       Appendix: Details on what to expect to be displayed when you setup your language 

      Language Locale Before Before  Now  Now
          Date Date Time Date Date Time
      English (US)
      Default + fallback
      en-US 2021/01/22 Jan 22, 2021, 1:11 PM Jan 22, 2021 Jan 22, 2021, 1:11 PM
      English (UK) en-GB 2021/01/22 Jan 22, 2021, 1:11 PM 22 Jan 2021 22 Jan 2021, 1:11 pm
      Chinese (Simplified)
      中文 (简体)
      zh-CN 2021/01/22 2021年1月22日下午1:11 2021年1月22日 2021年1月22日下午1:11
      Czech
      Čeština
      cs-CZ 2021/01/22 22. 1. 2021 1:11 odp. 22. 1. 2021 22. 1. 2021 1:11 odp.
      Danish
      Dansk
      da-DK 2021/01/22 22. jan. 2021 1.11 PM 22. jan. 2021 22. jan. 2021 1.11 PM
      Dutch
      Nederlands
      nl-NL 2021/01/22 22 jan. 2021 1:11 p.m. 22 jan. 2021 22 jan. 2021 1:11 p.m.
      Estonian
      Eesti
      et-EE 2021/01/22 22. jaan 2021 1:11 PM 22. jaan 2021 22. jaan 2021 1:11 PM
      Finnish
      Suomi
      fi-FI 2021/01/22 22. tammik. 2021 klo 1.11 ip. 22. tammik. 2021 22. tammik. 2021 klo 1.11 ip.
      French
      Français
      fr-FR 2021/01/22 22 janv. 2021, 1:11 PM 22 janv. 2021 22 janv. 2021, 1:11 PM
      German
      Deutsch
      de-DE 2021/01/22 22. Jan. 2021, 1:11 PM 22. Jan. 2021 22. Jan. 2021, 1:11 PM
      Hungarian
      Magyar
      hu-HU 2021/01/22 2021. jan. 22. du. 1:11 2021. jan. 22. 2021. jan. 22. du. 1:11
      Icelandic
      Íslenska
      is-IS 2021/01/22 22 Jan 2021, 1:11 pm 22 Jan 2021 22 Jan 2021, 1:11 pm
      Italian
      Italiano
      it-IT 2021/01/22 22 gen 2021, 1:11 PM 22 gen 2021 22 gen 2021, 1:11 PM
      Japanese
      日本語
      ja-JP 2021/01/22 2021年1月22日 午後1:11 2021年1月22日 2021年1月22日 午後1:11
      Korean
      한국어
      ko-KR 2021/01/22 2021년 1월 22일 오후 1:11 2021년 1월 22일 2021년 1월 22일 오후 1:11
      Norwegian
      Norsk
      nb-NO 2021/01/22 Jan 22, 2021, 1:11 PM 22. jan. 2021 22. jan. 2021, 1:11 p.m.
      Polish
      Polski
      pl-PL 2021/01/22 22 sty 2021, 1:11 PM 22 sty 2021 22 sty 2021, 1:11 PM
      Portuguese (Brazil)
      Português (Brasil)
      pt-BR 2021/01/22 22 de jan. de 2021 1:11 PM 22 de jan. de 2021 22 de jan. de 2021 1:11 PM
      Portuguese (Portugal)
      Português (Portugal)
      pt-PT 2021/01/22 22 de jan. de 2021 1:11 PM 22/01/2021 22/01/2021, 1:11 da tarde
      Romanian
      Română
      ro-RO 2021/01/22 22 ian. 2021, 1:11 p.m. 22 ian. 2021 22 ian. 2021, 1:11 p.m.
      Russian
      Русский
      ru-RU 2021/01/22 22 янв. 2021 г., 1:11 PM 22 янв. 2021 г. 22 янв. 2021 г., 1:11 PM
      Slovak
      Slovenčina
      sk-SK 2021/01/22 22. 1. 2021, 1:11 PM 22. 1. 2021 22. 1. 2021, 1:11 PM
      Spanish
      Español
      es-ES 2021/01/22 22 ene 2021 1:11 p. m. 22 ene 2021 22 ene 2021 1:11 p. m.
      Swedish
       
      sv-SE 2021/01/22 22 jan. 2021 1:11 em 22 jan. 2021 22 jan. 2021 1:11 em

      The Atlassian Product Team

       

      Atlassian Update on May 24th

      Hi all, thanks so much for the feedback on this ticket and the Atlassian team appreciates your patience as we build out an improvement on this issue

      Our research has shown that (1) significant portion of existing use cases for “date/time advanced settings” is to configure a date/time that makes sense for a specific location/country (2) cross geographic collaboration is a common and increasing use case that requires different date/time display between users within the same instance. To better adapt our product to this, we’ll progressively roll-out the following changes in upcoming days.

      • Users can now change the default edit and display of both date and date/time fieldsusing their language/locale setup (i.e. "en_AUS" or "Dutch") instead of being forced into the American month/day/year display only. Here’s how to setup yours: https://support.atlassian.com/atlassian-account/docs/manage-your-language-preferences/. For those using language not supported (i.e. Greek). We suggest you choose UK English as your preference to get the desired display of day/month/year.
      • As part of shifting such setting to the user level, in long term, we’ll remove the advanced admin setting of custom date/time format (which currently can be found under: System->User Interface->Look and feel->Date/time format). In the interim, warning message of “advanced date picker settings will no longer be supported” will appear.

       

      Summary

      When a custom date/time format has been configured and Jira is configured to use the new issue view, the custom date/time format is ignored and Jira displays the default date/time format.

      Environment

      • Jira Core

      Steps to Reproduce

      1. Configure a custom date/time format as shown here
      2. Navigate to an issue or select an issue from a board

      Expected Results

      • Custom date/time formats are displayed in the board/full issue views

      Actual Results

      • The default Jira date/time format is still displayed
      • Look and feel settings:
      Old view New view

      Notes

      • This issue doesn't occur in the old/existing issue view/board view
      • On Jira Core(Business) projects, there isn't an option to turn off the new issue view

      Workaround

      There is no current workaround

            [JRACLOUD-71304] New issue view: custom date/time format setting not respected in the new view

            So annoying here too as this bug is only for the cloud version.

            Someone would have thought that things will be better moving forward but not in this case.

            There are so many other annoying things with Jira cloud that do not make much sense to me also but they say that "this is how it works"

            For me, a developer, it is rather annoying.

            Deleted Account (Inactive) added a comment - So annoying here too as this bug is only for the cloud version. Someone would have thought that things will be better moving forward but not in this case. There are so many other annoying things with Jira cloud that do not make much sense to me also but they say that "this is how it works" For me, a developer, it is rather annoying.

            @strannikca: They don't care. Nobody at Atlassian gives any fucks about this BUG and they actively try to marked it as a needed feature. Everyone else sees what they are doing, but beside canceling every contract, there is little that we can do.

            The BUGFIX can be found as a new ticket here : https://jira.atlassian.com/browse/JRACLOUD-76814

            But in their eyes, it is just a wish from some stupid CUSTOMERS that won't accept this BUG as a feature.
            This BUG is known since 2019-01-03. They created the new "Suggestion" on 2021-06-10 and didn't do shit ever since.

            So be a good customer and just keep paying and stop demanding BUGFIXES please.

            Marek Schmidt added a comment - @strannikca: They don't care. Nobody at Atlassian gives any fucks about this BUG and they actively try to marked it as a needed feature. Everyone else sees what they are doing, but beside canceling every contract, there is little that we can do. The BUGFIX can be found as a new ticket here : https://jira.atlassian.com/browse/JRACLOUD-76814 But in their eyes, it is just a wish from some stupid CUSTOMERS that won't accept this BUG as a feature. This BUG is known since 2019-01-03. They created the new "Suggestion" on 2021-06-10 and didn't do shit ever since. So be a good customer and just keep paying and stop demanding BUGFIXES please.

            strannikca added a comment -

            This "workaround" doesn't help a lot. I need to have English language and normal for me date-time format, as well as week starting from Monday.

            strannikca added a comment - This "workaround" doesn't help a lot. I need to have English language and normal for me date-time format, as well as week starting from Monday.

            Yuan Jiang added a comment -

            b3574a68a193 workaround instruction is in the description section. Cross posted here as well 

             

            • Users can now change the default edit and display of both date and date/time fieldsusing their language/locale setup (i.e. "en_AUS" or "Dutch") instead of being forced into the American month/day/year display only. Here’s how to setup yours: https://support.atlassian.com/atlassian-account/docs/manage-your-language-preferences/.
            • For those using language not supported (i.e. Greek). We suggest you choose UK English as your preference to get the desired display of day/month/year.

             

            Yuan Jiang added a comment - b3574a68a193  workaround instruction is in the description section. Cross posted here as well    Users can now change the  default edit and display of both date and date/time fields ,  using their language/locale setup (i.e. "en_AUS" or "Dutch")  instead of being forced into the American month/day/year display only. Here’s how to setup yours:  https://support.atlassian.com/atlassian-account/docs/manage-your-language-preferences/ . For those using language not supported (i.e. Greek). We suggest you choose UK English as your preference to get the desired display of day/month/year.  

            S Fong added a comment - - edited

            where is the workaround documentation?

            S Fong added a comment - - edited where is the workaround documentation?

            Yuan Jiang added a comment - - edited

            Hi everyone, thanks again for the interest on this ticket. We’re marking this ticket as closed now because a workaround has been released to solve the issue of "users always being forced into the American format of mm/dd/yyyy" by allowing each user to format their dates and times on the new issue view based on their language preferences. For many of you, this workaround solved the problem.

             

            Workaround instruction

            • Users can now change the default edit and display of both date and date/time fieldsusing their language/locale setup (i.e. "en_AUS" or "Dutch") instead of being forced into the American month/day/year display only. Here’s how to setup yours: https://support.atlassian.com/atlassian-account/docs/manage-your-language-preferences/.
            • For those using language not supported (i.e. Greek). We suggest you choose UK English as your preference to get the desired display of day/month/year.

             

            For those customers that still face challenges with this solution we have opened a new ticket where we will gather interest specifically on when the user level language based settings is not a viable solution. Please comment on this new ticket https://jira.atlassian.com/browse/JRACLOUD-76814 to let us know your specific use case (i.e. why it’s important to have a specific date/time settings, and whether you’d like it at admin or user level), so we can ensure the experience we release works for you.

            For those concerned about their calendar locking Sunday as the first day of the week, watch and comment on this ticket: https://jira.atlassian.com/browse/JRACLOUD-71611 

             

            The Atlassian Product Team

            Yuan Jiang added a comment - - edited Hi everyone, thanks again for the interest on this ticket. We’re marking this ticket as closed now because a workaround has been released to solve the issue of "users always being forced into the American format of mm/dd/yyyy" by allowing each user to format their dates and times on the new issue view based on their language preferences. For many of you, this workaround solved the problem.   Workaround instruction Users can now change the  default edit and display of both date and date/time fields ,  using their language/locale setup (i.e. "en_AUS" or "Dutch")  instead of being forced into the American month/day/year display only. Here’s how to setup yours:  https://support.atlassian.com/atlassian-account/docs/manage-your-language-preferences/ . For those using language not supported (i.e. Greek). We suggest you choose UK English as your preference to get the desired display of day/month/year.   For those customers that still face challenges with this solution we have opened a new ticket where we will gather interest specifically on when the user level language based settings is not a viable solution. Please comment on this new ticket  https://jira.atlassian.com/browse/JRACLOUD-76814  to let us know your specific use case (i.e. why it’s important to have a specific date/time settings, and whether you’d like it at admin or user level), so we can ensure the experience we release works for you. For those concerned about their calendar locking Sunday as the first day of the week, watch and comment on this ticket:  https://jira.atlassian.com/browse/JRACLOUD-71611     The Atlassian Product Team

            @yjiang@atlassian.com, thank you for your recent update, but what about the following setting that is currently set under /secure/admin/LookAndFeel!default.jspa and is still ignored by the New Issue View. You recent update appears not to mention solving this issue, unless I have missed this?.. 

            • Use ISO8601 standard in Date Picker
              Turning it on will cause Monday to be the first day of week in the Date Picker, as specified by the ISO8601 standard

            We would like the New Issue View Date Picker to respect this setting and display the Date Picker calendar as Mon to Sun, rather than Sun - Mon, as it does currently.

            Ivan Shtanichev added a comment - @ yjiang@atlassian.com , thank you for your recent update, but what about the following setting that is currently set under  /secure/admin/LookAndFeel!default.jspa and is still ignored by the New Issue View. You recent update appears not to mention solving this issue, unless I have missed this?..  Use ISO8601 standard in Date Picker Turning it on will cause Monday to be the first day of week in the Date Picker, as specified by the ISO8601 standard We would like the New Issue View Date Picker to respect this setting and display the Date Picker calendar as Mon to Sun, rather than Sun - Mon, as it does currently.

            I agree with the comment above from a usability point of view the old view is so much better!

            Florence Quelle added a comment - I agree with the comment above from a usability point of view the old view is so much better!

            SBC added a comment -

            Disclaimer: Sarcasm may occur...

            Rest assured that the skilled folks at Atlassian are certainly working on this (from https://jira.atlassian.com/browse/JRACLOUD-68381):

            SBC added a comment - Disclaimer: Sarcasm may occur... Rest assured that the skilled folks at Atlassian are certainly working on this (from  https://jira.atlassian.com/browse/JRACLOUD-68381):

            @yjiang@atlassian.com Any time estimate on when this and related issues in new view/next-gen projects could be fixed?

            Peter Galiovský added a comment - @ yjiang@atlassian.com Any time estimate on when this and related issues in new view/next-gen projects could be fixed?

            i agree with mark wheeler - Atlassian should give people the option - the old view is so much better

            Rob Pellegriti added a comment - i agree with mark wheeler - Atlassian should give people the option - the old view is so much better

            I hope the "New Issue  View" forced migration has been worth it for Atlassian.  I had to apologise to my Jira users yesterday for the new view which is being enforced on them today.  I was hoping it was a bad April Fool's joke but sadly not I suspect.

            Mark Wheeler added a comment - I hope the "New Issue  View" forced migration has been worth it for Atlassian.  I had to apologise to my Jira users yesterday for the new view which is being enforced on them today.  I was hoping it was a bad April Fool's joke but sadly not I suspect.

            They said it was going to be fixed BEFORE the force of the New Issue View but its not, thats a No-Go!

            In the Details its still shown as YYYY/MM/DD, but when I click on the datepicker it changes to MM/DD/YYYY but on the bottom of the details screen it is shown like "01. April 2021"

            What is that?

             

            Dennis Möller added a comment - They said it was going to be fixed BEFORE the force of the New Issue View but its not, thats a No-Go! In the Details its still shown as YYYY/MM/DD, but when I click on the datepicker it changes to MM/DD/YYYY but on the bottom of the details screen it is shown like "01. April 2021" What is that?  

            This needs to be fixed asap. Its ridiculous that it is considered low priority. We talking basic functionality here...

            Deleted Account (Inactive) added a comment - This needs to be fixed asap. Its ridiculous that it is considered low priority. We talking basic functionality here...

            I agree that this needs to be addressed sooner rather than later

            Patrick Girgenti added a comment - I agree that this needs to be addressed sooner rather than later

            Ricardo N added a comment -

            Ricardo N added a comment - https://getsupport.atlassian.com/browse/PCS-26917  

            Me to - why is it low priority, we can't add a date after January, this is urgent, it affects many users

            Dorotea Böhm added a comment - Me to - why is it low priority, we can't add a date after January, this is urgent, it affects many users

            S Fong added a comment -

            Ditto - I agree with SBC and Rob.  

            S Fong added a comment - Ditto - I agree with SBC and Rob.  

            Rob Pellegriti added a comment - - edited

            I agree with SBC - this needs to be fixed. 

            why is it low priority?

            Rob Pellegriti added a comment - - edited I agree with SBC - this needs to be fixed.  why is it low priority?

            SBC added a comment -

            Please escalate this issue to high priority, now that we are forced to use the new view.

             

            SBC added a comment - Please escalate this issue to high priority, now that we are forced to use the new view.  

            With the forced migration to new view, this workaround is no longer relevant. Please fix.

            We are seeing American date format here in an Australian team.  On the same screen we can see both middle endian mm-dd-yyyy and format and small endian date format (dd-mm-yyyy)! So much wasted time due to someone not asking "is it the 11th of the December or 12th of the November"?

            Life was so much simpler when Atlassian just used big endian format everywhere (e.g. yyyy-mm-dd) as nobody does (yyyy-dd-mm).

            James Rickards (Deloitte) added a comment - - edited With the forced migration to new view, this workaround is no longer relevant. Please fix. We are seeing American date format here in an Australian team.  On the same screen we can see both middle endian mm-dd-yyyy and format and small endian date format (dd-mm-yyyy)! So much wasted time due to someone not asking "is it the 11th of the December or 12th of the November"? Life was so much simpler when Atlassian just used big endian format everywhere (e.g. yyyy-mm-dd) as nobody does (yyyy-dd-mm).

            Please fix this asap

            Sandra Axelsdottir added a comment - Please fix this asap

            https://nz.linkedin.com/in/canham   Matthew can you help us resolve this bug please?

            John Driscoll added a comment - https://nz.linkedin.com/in/canham    Matthew can you help us resolve this bug please?

            SBC added a comment -

            Soon we can celebrate three years "birthday" of this original issue JIRACLOUD-68381.

            How hard can it be to get it fixed?

            It should be obvious to everybody how annoying this is in everyday use of Jira.

            Atlassian is so focused on bringing out new features in the pursuit for new customers. How about working a bit more on keeping existing customers happy?

            SBC added a comment - Soon we can celebrate three years "birthday" of this original issue JIRACLOUD-68381. How hard can it be to get it fixed? It should be obvious to everybody how annoying this is in everyday use of Jira. Atlassian is so focused on bringing out new features in the pursuit for new customers. How about working a bit more on keeping existing customers happy?

            In the USA, the common convention for displaying date values is mm/dd/yyyy  or MON-dd-yyyy or even in some cases dd-MON-yyyy.  We have our default values configured to display the date values "properly" however, Jira fails to display the date values on individual issues the way we've configured the default values.    This causes confusion for end-users and is adversely affecting user adoption of the Jira tool.  Please see the example attached here.  Resolving this glitch in displaying dates would be greatly appreciated.

            John Driscoll added a comment - In the USA, the common convention for displaying date values is mm/dd/yyyy  or MON-dd-yyyy or even in some cases dd-MON-yyyy.  We have our default values configured to display the date values "properly" however, Jira fails to display the date values on individual issues the way we've configured the default values.    This causes confusion for end-users and is adversely affecting user adoption of the Jira tool.   Please see the example attached here.  Resolving this glitch in displaying dates would be greatly appreciated.

            Now there is no old issue view this should be higher priority

            Aiden Marriott added a comment - Now there is no old issue view this should be higher priority

            Please fix this as soon as possible, Jira team.

            Chris Cunnington added a comment - Please fix this as soon as possible, Jira team.

            Timo Laru added a comment -

            Seems the same problem applies to old-style issue view as well, at least in our Jira instance. 

            Changed date formats from "d/m/y"ish to "d MMM y"ish, and time format from 12h to 24h, disabled the new-style issue view, and still see the default date & time formats being used everywhere. That is, the suggested workaround doesn't seem to have any effect.

             

             

            Timo Laru added a comment - Seems the same problem applies to old-style issue view as well, at least in our Jira instance.  Changed date formats from "d/m/y"ish to "d MMM y"ish, and time format from 12h to 24h, disabled the new-style issue view, and still see the default date & time formats being used everywhere. That is, the suggested workaround doesn't seem to have any effect.    

            Fernando added a comment -

            I also have the same problem. When we try to insert time record in time tracking, the date and time field does not respect the settings. Awaiting a resolution of this case the fastest. Thank you.

            Fernando added a comment - I also have the same problem. When we try to insert time record in time tracking, the date and time field does not respect the settings. Awaiting a resolution of this case the fastest. Thank you.

              yjiang@atlassian.com Yuan Jiang
              dnguyen4 Derrick Nguyen
              Votes:
              143 Vote for this issue
              Watchers:
              163 Start watching this issue

                Created:
                Updated:
                Resolved: