Hi there,
We have noticed that no matter where someone is the forms date format is mm/dd/yyyy.
This is fine for our US studio but in Australia people are mentioning it. For me all my other date fields in JSM show dd/mm/yyyy except what comes on on the forms.
Is this a hard locked in format or where would I tell forms specifically to understand the timezone I am in.
Cheers.
Hi Steven,
I'm afraid this is a system-wide setting that can be controlled by setting the jira.date.picker.javascript.format.
Here is an overview of notations in case you want to change the setting.
If your users are confused by the date format I recommend the ISO 8601 which is: year-month-day. The chance of mixing up months and days is less likely this way.
Or you could use the day-month-year notation where month shows the 3 first letters.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Via system -> general configuration -> advanced settings
Direct url: https://<your-subdomain>.atlassian.net/secure/admin/AdvancedApplicationProperties.jspa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ah it seems we are already setup like that. "
is already in place.
JSM date fields being added via 'Forms' must have a hard date format that they stick to which is mm/dd/yyyy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1, we're seeing mm/dd/yyyy format for JSM Forms, system settings for java.date.picker are dd/mm/yyyy laid out exactly as described in this thread. All other site settings are correct for time zones, etc. User profile settings are also correct of the land of Oz.
I'm unable to locate a Bug ticket for this. Has anyone reported it?
Cheers,
PeterQ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is a PUBLIC bug for this :
https://jira.atlassian.com/browse/JSDCLOUD-13495
Workaround
This issue is not seen when we use the "Date and Time Field" in the FORM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
https://jira.atlassian.com/browse/JSDCLOUD-13495 - Bug has been raised please add yourself as a watcher
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Workaround
This issue is not seen when we use the "Date and Time Field" in the FORM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, we are having the same issue in forms. How do we resolve this please?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.