Michiel Beijen schrieb:
> http://bugs.otrs.org/show_bug.cgi?id=4419
>
> OTRS uses the same date object for searches as for pending dates. For
> searches, it makes sense to be able to search for older tickets. For
> pending dates, dates in the past don't make as much sense.
> If you want to address this you'd need to change quite a few files,
> therefore we decided to address the issue in the upcoming major release
> of otrs, and not address it in the 2.4.x branch. Also, apparently many
> customers can work with it happily the way it is now...
Or better, they fixed it themselves. :)
Why not make this a configurable option, like this:
$Param{DateString} = $Self->{LayoutObject}->BuildDateSelection(
Format => 'DateInputFormatLong',
DiffTime =>
$Self->{ConfigObject}->Get('Ticket::Frontend::PendingDiffTime') || 0,
YearPeriodPast =>
$Self->{ConfigObject}->Get('Ticket::Frontend::PendingYearPeriodPast') || 0,
YearPeriodFuture =>
$Self->{ConfigObject}->Get('Ticket::Frontend::PendingYearPeriodFuture')
|| 5,
%Param,
);
Surely, Kernel/Defaults.pm would need those two new Config Options, too,
which would render the "|| x" part unnecessary, too (despite so. has the
idea of undef'ing them ;) which noone should do with OTRS' config values
nonetheless).
I've always been thinking about hard-coded values of that kind as of a
lazy thing to do :) *waves*
Btw, I'd vote for seeing this in the 2.4 series.
With highest regards,
Robert Kehl
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/
