New issue view: custom date/time format setting not respected in the new view

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 

The Atlassian Product Team

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

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