DateTime custom field display issues

RT Users
1

hello everyone,
some time ago I asked my team member to investigate problem with display
format of DateTime custom fields, but unfortunately he failed - so I
have to fix it myself… ((-:
I am using a few DateTime fields to mark some actions. they are rendered
correctly in Ticket preview/summary but in searches they are shown in
default ISO/UTC format.
here is an example (excerpt from search page source):

WRO Grunwaldzka 2012-09-26 13:56:00 2012-10-17 11:05:00 Priorytet 3 2012-10-27 17:37

first 2 dates are custom fields and the last one is system bulitin
"Resolved" value.
in RT_SiteConfig.pm I have set following variables:
Set($Timezone, “Europe/Warsaw”);
Set($DateTimeFormat, { Format => “ISO”, Timezone => “server”, Seconds =>
0 });

as you can see RT follows this setting for system fields but ignores it
for Custom Field.

in Ticket/Display everything is OK:

Pocz�tek awarii: 2012-09-26 15:56 Koniec awarii: 2012-10-17 13:05

please help me fix this.

best regards,
Alek

2

rt-users-request@lists.bestpractical.com pisze, W dniu 2012-10-29 17:00:

hello everyone,
some time ago I asked my team member to investigate problem with display
format of DateTime custom fields, but unfortunately he failed - so I
have to fix it myself… ((-:
I am using a few DateTime fields to mark some actions. they are rendered
correctly in Ticket preview/summary but in searches they are shown in
default ISO/UTC format.

hi,
has anyone seen this issue in you installations or am I the only case?

cheers,
Alek

3

rt-users-request@lists.bestpractical.com pisze, W dniu 2012-10-29 17:00:

hello everyone,
some time ago I asked my team member to investigate problem with display
format of DateTime custom fields, but unfortunately he failed - so I
have to fix it myself… ((-:
I am using a few DateTime fields to mark some actions. they are rendered
correctly in Ticket preview/summary but in searches they are shown in
default ISO/UTC format.

has anyone seen this issue in you installations or am I the only case?

I suspect you’re running into the problem that the search result formats
are just printing out the value of the custom field, not running it
through the formatters. I thought there was a bug open about using the
more standard renderers for CFs in 4.2, but I can’t easily find it.

You’ll find the relevant code in Elements/ColumnMap (search for
CustomField), and you could use a callback to fix your CFs locally
until such time as they’re sorted out in core.

-kevin