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

Invalid Date Format for Riga timezone

XMLWordPrintable

      Steps to Reproduce

      1. Set the JAVA Opts in setenv.sh or setenv.bat 
        -Duser.timezone=Europe/Riga
      2. Start JIRA
      3. Go to due date, entered the value 01.04.1984
        Happens to other date field as well.

      Expected behaviour:

      The field value accepted by JIRA correctly

      Actual Behaviour:

      The value is not accepted and prompt error:

      You did not enter a valid date. Please enter the date in the format "d/MMM/yy", eg. "5/Aug/14"

      So far only 1 date affected. Eg. 1/Apr/1984.

      Workaround:

      • If your OS timezone is Riga:
        • Force JVM to run in another timezone that in the same time: 
          -Duser.timezone=Europe/Helsinki
        • Switch the OS timezone to another timezone
      • In date time field, put date with time e.g: 01.04.1984 01:00 then it works correctly.

            [JRASERVER-39470] Invalid Date Format for Riga timezone

            Ewelina Fiedorowicz added a comment -
            Atlassian Update – 22.07.2021

            Hi Everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,
            Ewelina Fiedorowicz

            Ewelina Fiedorowicz added a comment - Atlassian Update – 22.07.2021 Hi Everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ewelina Fiedorowicz

              Unassigned Unassigned
              yen@atlassian.com TeckEn (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: