A further wrinkle: After the user submits the issue with the due_date filled in, when we try to advance the issue to the next state (using Change Status To), the due_date is cleared on the change status screen.
I think I am going to submit a bug for this behavior. The users are not happy because their data is being wiped out. I may have to downgrade back to 2.22.2 because of this.
Default value for due date not work
Moderators: Developer, Contributor
Re: Default value for due date not work
I have just figured out the problem is due to the custom date format bug previously reported as #0022558. When I remove the following lines from our config_inc.php, the default for due_date works.
$g_short_date_format = 'd-M-Y';
$g_normal_date_format = 'd-M-Y H:i';
$g_complete_date_format = 'd-M-Y H:i';
Another symptom of #0022558 is that with the customized date formats, the update and change status pages clear out the existing value for due_date. If you complete the update or the status change, a value of "1" is recorded in the database, as noted earlier in this topic. This is a loss of data which is unacceptable.
Please note that the bugfix in date_patch.txt in #0022558 does not work for me.
$g_short_date_format = 'd-M-Y';
$g_normal_date_format = 'd-M-Y H:i';
$g_complete_date_format = 'd-M-Y H:i';
Another symptom of #0022558 is that with the customized date formats, the update and change status pages clear out the existing value for due_date. If you complete the update or the status change, a value of "1" is recorded in the database, as noted earlier in this topic. This is a loss of data which is unacceptable.
Please note that the bugfix in date_patch.txt in #0022558 does not work for me.