I try tı selecet the due date value. But when I select date and press create button. ı take below error.
You did not enter a valid date. Please enter the date in the format "d/MMM/yy", eg. "28/Eyl/20"
I think it has to do with the translation from English to Turkish(?). The example is showing the non-English version of the date, while the due date field is showing Sep instead.
Can you try whether changing Sep to Eyl manually gets rid of the error?
If so, I'd raise a bug request with Atlassian via support.atlassian.com/contact/
I've created a bug report for this.
If this solved your situation for now (using the workaround until a fix is implemented), please consider marking my answer as accepted so others with the same problem can find it more easily :)
Have a nice day!
Sorry to hear that this date picker seems to not behave as expected here. I tried to recreate this problem in order to better understand it. From my testing I had to follow a number of steps to try to get this same error.
In that setup I was able to reproducethis once. But I found that waiting a few minutes and reloading the page creates a different result. It appears that when a user changes their language selection there, the corresponding Jira elements like date/time picker do get updated, but not on existing pages you might already loaded in your browser. Instead you need to refresh/reload that page after making a change like this in order to be able to see the correct date picker, like so:
In short, I believe there is an expectation that when a user changes their language/region preference within Atlassian Cloud, that they would need to refresh any open pages in order for those settings to take affect. Changing a language preference in Atlassian Cloud does take time for this preference to propigate itself down to all the different services in which your account might use an application that has language cusomizations of this nature.
In which case, I don't know that this is technically bug. That said I am interested to see if there is perhaps a way you can harden your Jira site configuration to avoid this problem entirely.
For example, I found that I could prevent this problem entirely, by adjusting the date input formats, and the picker formats to only use numbers when users enter date data (and not strings like 'Sep' or 'Eyl'). You could do this by going to Gear icon > System > General Configuration and then click the Advanced Settings button at the top of that page. On this page you can change
|dd/MM/yyyy h:mm a|
|%e/%m/%Y %I:%M %p|
or like so:
But by changing these values in the advanced settings, the date picker no longer needs to rely upon the strings of month names that will commonly be different between user selected languages.
I hope this helps.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events