Hi Torsten,
try this:
my $DUEDATE = $self-TicketObj-FirstCustomFieldValue('Date');
my $DUETIME = $self-TicketObj-FirstCustomFieldValue('Time');
my $DUE = $DUEDATE. .$DUETIME;
my $DATE = RT::Date-new( $session{'CurrentUser'} );
$DATE-Set(
Format = 'unknown',
Value = $DUE,
Timezone =
Hi Chris,
this i already tried. The problem is more that the timezone offset is only
for display, not for calculation used (so far i figured already) and i have
really no idea how to fix it. one possible way could be:
1. If a user is entering this fields, check the users timezone and use the
Hi Torsten,
normally you don't need to worry about timezones in date calculations.
You should always normalize all dates to UTC and then do the calculations.
May you can give an example of you date calculations?
Chris
Am 01.07.2010 14:10, schrieb Torsten Brumm:
Hi Chris,
this i already
Hi.
I think you want to construct date object using user who set those cfs and
use timezone user. SetDue method has no diff between 3.6 and 3.8, it takes
ISO in utc.
01.07.2010 16:11 пользователь Torsten Brumm torsten.br...@googlemail.com
написал:
Hi Chris,
this i already tried. The problem is
Hi RT Users,
since we are planing our RT 3.8 migration, we are cross checking all our
scrips and some scrips with time calculaltions driving me mad.
Example from RT 3.6.x
We have two CF's: Date and the other Time
CF.Date
CF.Time
The user is entering the date and the time in utc normally - our
