URL: https://jira.domain.tdl/secure/admin/AdvancedApplicationProperties.jspa
Jira Version: 7.9.0
System: Ubuntu 16.04 Docker Compose
Database: PostgreSQL
# jira.date.picker.java.format
English default:
This part is only for the Java (server side) generated dates. Note that this should correspond to the javascript date picker format (jira.date.picker.javascript.format) setting.
German translation:
Dieser Teil bezieht sich nur auf die von Java (Server) erstellten Datumsangaben. Bitte beachten Sie, dass diese dem JavaScript- Datums-/Zeitauswahlformat entsprechen müssen (jira.date.time.picker.javascript.format).
# Should be:
English default:
This part is only for the Java (server side) generated dates. Note that this should correspond to the java date picker format (jira.date.picker.java.format) setting.
German translation:
Dieser Teil bezieht sich nur auf die von Java (Server) erstellten Datumsangaben. Bitte beachten Sie, dass diese dem Java-Datums-/Zeitauswahlformat entsprechen müssen (jira.date.picker.java.format).
A similar problem occurs in:
# jira.date.picker.javascript.format
# jira.date.time.picker.java.format
Hi Lukas,
I understand that you would like to suggest an alternative in regards to the German translation of certain system elements in Jira when viewing the administration panel.
However this is not something that I can change myself. The good news is that we do have another location where you can submit these alternative translations yourself. Please see our Translations site. Specifically, you can search for key terms such as in this link
You can then use the 'retranslate' link on that page to offer your alternative translation for this specific element. If this is accepted, then I would expect this translation to be included in a future language pack that is bundled with Jira installations. Thanks for helping to improve our translations.
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so I think I understand better now. But I think I found a different problem here. If I understand your updated post, you believe that the java time format should correspond to the java, instead of Javascript.
However that part is actually correct. The server side java format should correspond to the client side javascript formats for things to work correctly. The complicating part that I think is confusing matters here is that Jira has both date and date/time fields to have to manage. As a result these technically could be in different formats. The problem I found is in regards to the details of the element is translated differently for German.
In English is states:
jira.date.picker.javascript.format
(which is correct) But in the current German language pack it is incorrectly translated to:
jira.date.time.picker.javascript.format
As a result, there is a problem here. But I think we currently disagree on what that problem is. I hope I have explained this well. Please let me know your thoughts on this.
Thanks
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1 + 3 = Java Simple Date Format
labled as jira.date.picker.java.format and jira.time.picker.java.format
2 + 4 = Unix Date Format
anyway both should be replaced with ISO_8601
see:
https://en.wikipedia.org/wiki/ISO_8601
https://docs.oracle.com/javase/tutorial/i18n/format/simpleDateFormat.html
https://confluence.atlassian.com/jira/changing-the-due-date-input-format-192536.html
https://www.cyberciti.biz/faq/linux-unix-formatting-dates-for-display/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can see a problem with your current settings. Based on the format you have in #1, I believe that #2 should instead be:
%e.%b.%y
(without spaces, and with the missing '.') This format has to correspond to the Java format in #1.
Also given the way you have formatted #3 there is another problem. Since you have dropped the 'a' from the Java format this eliminates the AM/PM from the time. The problem is that when using the lower case 'h' here, you have no way to represent hours 13-23. In turn we have to look back at java documentation you cited in https://docs.oracle.com/javase/tutorial/i18n/format/simpleDateFormat.html
Instead #3 I think should be changed to
dd.MMM.yy H:mm
The capitalized 'H' will provide the time in 24 hour format (0-23).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the remind for 24 hour support but its not the point here to make it clear my jira works wonderful.
Look at my email adress, i know a lot of programming and this is a damn huge problem to fix.
About 2 days of work.
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.
For the friendly remind on the 24 hours bug, i remind you to read the post of jarnbjo,
https://stackoverflow.com/questions/2201925/converting-iso-8601-compliant-string-to-java-util-date
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It still looks like a mis-configuration to me. The SO post just implies your chosen formats are wrong.
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.
Nor would I, I don't think making a minor correction to a configuration setting is worth that much.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Problem with saying "it's a system wide bug" is that you cannot know that without wider testing. It works fine for me, off-the-shelf. It works fine for a lot of other people too.
It might well be a bug, but if it is, it needs to be shown that it is.
When I try the settings Andrew provided, it works for me (well, not quite, because I'm in the wrong timezone, but it does leave me with data that clearly matches being in the wrong one).
Have you tried correcting your settings? Do you get the same problem when you have?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes I can,
The Java time-scale is used for all date-time classes. This includes Instant
, LocalDate
, LocalTime
, OffsetDateTime
, ZonedDateTime
and Duration
.
according to this Document java.util.Date and java.text.SimpleDateFormat is not longer part of the Java date-time classes.
See:
https://docs.oracle.com/javase/9/docs/api/java/time/Instant.html
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.