Redmine

I tried a little change in caldendar-fi.js file:
Calendar._TT["DEF_DATE_FORMAT"] = "%Y-%m-%d"
==>
Calendar._TT["DEF_DATE_FORMAT"] = "%d.%m.%Y"

Did not change the behaviour though :) The date format was still YYYY-MM-DD

Not really a programmer so no clue why the change didn't work. Anyways tried with several browsers so might need change to some other place to change the date format.

aah.. i tried those too, and some other tricks... but best I got was calendar-widget changing the field correctly (respecting dd-mm-yyyy) when I clicked a date.. but still, everytime I am adding new issue, or editing old one, the date in field gets defaulted in wrong order.

I dont know ruby, so after hour of going through sources I just gave up :)

.b

Patch #6450 solves the problem for user input in the Custom Value model. Diff has been attached to #6450.

This was a major pain point for some of my colleagues using Redmine - hopefully this fix will eliminate the issue on user input across the board for custom fields.

The defect is in Redmine 2.4.2 too.

+1

+1

+1

+1

I created a jquery plugin to solve this problem:
jQuery Binding Format

+1

+1

Leandro, can you please explain how to use your jquery plugin with standard Redmine date fields?
Have you ever integrate it to Redmine?
Thanks

+1

+1

+1

+1.

We're currently upgrading from Redmine 2.4.3 to 3.4.6.stable, and it strikes me that this input date formatting problem is around for so long. So for us, it got worse:

• Our output date formatting is dd/MM/yyyy
• In 2.4.3 you get a calendar icon next to the input field. When selecting a date, it copies it in the input field in the format yyyy-MM-dd
• In 3.4.6 there is no calendar icon. The calendar shows up directly when clicking the input field. When selecting a date, it copies it in the input field in the format MM/dd/yyyy.

"yyyy-MM-dd" is still clear to us, at least it doesn't switch the month and the day.

What is more: when entering a date manually (the mask is MM/dd/yyyy), it applies a "ceiling" function to each date part. So when mistakenly typing e.g. 18, 05, 2018, meaning May 18, 2018, the 18 is converted automatically to 12, and without any warning it is set to 12/05/2018 (December 5th).

Unacceptable :)