Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-16508

Date format error when trying to start sprint while using Portuguese and Czech

XMLWordPrintable

      Summary

      Date format error when trying to start sprint while using Portugese/Czech due to capital letter in the month abbreviation.

      '19/Jan/18 12:39 PM' não é uma data válida. Por favor insira a data no seguinte formato: dd/MMM/yy h:mm a

       

      Steps to reproduce

      1. Login to an instance.
      2. Change language in profile preferences to Portugese/Czech language.
      3. Create a sprint.
      4. Start the sprint by selecting End Date to be at any date in any month.

      Current result

      Error is thrown mentioning the date selected is invalid.

      Expected result

      The month abbreviation should be returned in all lowercases and sprint can be started.

      Workaround

      1. Select Custom instead of default duration.
      2. Set the date accordingly.
      3. If the Custom selection is defaulted back to one of the template duration, change the minute by a few to avoid the revert.

      OR

      1. Set profile language to English temporarily.
      2. Start the sprint.
      3. Change profile language back to Portugese/Czech.

      This affect start date as well if the date is edited.

        1. portugese_month.PNG
          portugese_month.PNG
          18 kB

            [JSWCLOUD-16508] Date format error when trying to start sprint while using Portuguese and Czech

            Dylan added a comment -

            Hi all,

            Thank you for 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.

            Dylan added a comment - Hi all, Thank you for 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.

            Fernando Verly added a comment -

            The workaround suggested does not work

            Fernando Verly added a comment - The workaround suggested does not work

              Unassigned Unassigned
              mfahd Fahd
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: