Hi,
Im system administrator of our Jira Cloud.
I have an issue with one of our employees.
When she creates an issue, she cannot set due date, as it says the formaet is not correct.
Its set to be dd/MMM/yy. But she has to do this: dd/MMM./yy
Everybody else in the Jira project do not have the issue. ONLY this user.
I have set the follow dates in advanced. I cannot figure out how to solve her issue.
If she afterwards enters the issue, se is allowed to make a due date, and the date settings is then dd/MMM/yy - i do really not get why.
Does someone have a take on how I can solve this for her?
Advanced setup:
dd/MMM/yy
%d/%b/%y
dd/MMM/yy
%e/%b/%y
Hi Magnus
No we did not find a solution for this.
I have tried all above as Aylin suggest, but nothing works.
It is only one user. Every other does not have the problem. I have removed her profile and it have the same issue.
Soo... i gave up :-(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think I have found a solution that seems to work for everyone.
In the advanced settings I was able to find this field jira.date.picker.javascript.format, which dictates the format in the client. By adding the dot after month, as shown below:
I tested by creating an issue from my own account and also from another user from the portal - both worked out, without complains.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Magnus
I have an update.
I made the changes and it seems to work for her. But the change did that other accounts could not create delivery date. I found that the language was set to Danish under Personal settings. If i the clicked on the 'Profile settings'
The language was set to 'English (US)'. Therefore there was a need for '.' as you mentioned, but if it has danish settings it must be set to Danish.
Best regards
Simon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Simon!
Could you please attach a screenshot of the issue? I can't figure out what is she setting and the error that she gets.
Thanks! Aylin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again,
I have now attached an screenshot of the issue. This is when she 'create' a new issue. As you can see it presents the wrong format, even though it is correctly setted up (what I know of).
If she creates the issue, and the afterwards clicks on the due date (Afleveringsdato), she now can insert the correct date.
Any other users in the same project, do not have a similar issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Simon.
Unfortunately I don't know what could be happening, but I see that she is using jira's new look and feel, and I personally experienced several mistakes using it; so, even if it's just to verify, if you want you can try switching it off and see if it continues to happen or not.
You can switch it of from Personal Settings.
Hope it helps!
Regards, Aylin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aylin,
First of all, thank you for replies.
I have now tried to switch of for the ''Jira Labs'. It did unfortunately not make any difference. Do you have any other ideas?
Regards Simon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.