Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-37854

Basic search date picker suggestion doesn't respect date format settings

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

      summary

      Regardless of the date format set in JIRA (both in Look & Feel and Advanced Settings), the suggestion in the date picker in Basic Search will be displayed in the dd-MMM-yy format.

      steps to reproduce
      1. modify the Date/Time display format under JIRA Admin > System > Look and Feel, e.g. set it to yy-MMM-dd;
      2. change the date picker formats (jira.date.time.picker.java.format, jira.date.time.picker.javascript.format) under Advanced Settings accordingly;
      3. in Basic Search in the Issue Navigator, add a Date/time fields to the conditions;
      4. expand the field to populate it.

      Expected result: the suggestion in the date field respects the system settings.

      Actual result: the suggestion is always displayed in the dd-MMM-yy format. If a user follows it, an error message is displayed:

          Form Name

            [JRACLOUD-37854] Basic search date picker suggestion doesn't respect date format settings

            Tair Tidhar made changes -
            Component/s Original: Issue - Navigation [ 46635 ]
            Tair Tidhar made changes -
            Component/s New: Issue - Search - Frontend only [ 77950 ]
            Matthew Hunter made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Matthew Hunter made changes -
            Labels Original: affects-cloud affects-server seems_good New: affects-cloud affects-server seems_good timeout-bulk-close202304

            Atlassian Update - April 14, 2023

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - April 14, 2023 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team
            Anusha Rutnam made changes -
            Security Original: Reporter and Atlassian Staff [ 10751 ]
            abuse-antispam-bot made changes -
            Security New: Reporter and Atlassian Staff [ 10751 ]
            Mykola Iliushyn made changes -
            Labels Original: affects-cloud affects-server New: affects-cloud affects-server seems_good
            SET Analytics Bot made changes -
            UIS Original: 12 New: 0
            SET Analytics Bot made changes -
            UIS New: 12

              Unassigned Unassigned
              dwierzbicka Dobroslawa Wierzbicka (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: