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

Configuring the Time Look and Feel to MM/dd/yyyy causes the time fields in advanced search to display 0020 instead of 2020

XMLWordPrintable

      Issue Summary

      Configuring the Time Look and Feel to MM/dd/yyyy causes the time fields in advanced search to display 0020 instead of 2020

      Steps to Reproduce

      1. Go to the look and feel advanced settings and update the date picker format to MM/dd/yyyy
      2. Adjust the javascript format as well to read the %m%d%y

      Expected Results

      The JQL advanced search should display the year as 2020

      Actual Results

      When advanced searching issues and using a timestamp field, the resolver changes the year to 0020 instead of 2020

      Workaround

      The JQL has problems to resolve the yyyy, changing to yy works but there are issues when importing issues using CSV.

            [JRACLOUD-75724] Configuring the Time Look and Feel to MM/dd/yyyy causes the time fields in advanced search to display 0020 instead of 2020

            Matthew Hunter added a comment -
            Atlassian Update - January 21, 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 - January 21, 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

              gcardoso@atlassian.com Gonçalo Cardoso
              dbraun@atlassian.com Douglas B (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: