I have been looking at the possibility of changing/configuring OTRS to use UTC time natively.  As you may have seen from my posts on the otrs list, I started out thinking it was just a matter of configuration.  <br><br>Getting the UTC values in the database was pretty simple.  Getting them back to the user in a localized time (when the DB is in UTC, the server is +/-X TZ and the client browser is in +/-Y TZ) seems to be a bit trickier.<br>
<br>For one thing, it appears that the localization of time is actually being applied twice, during both the ticket object retrieval and and during the dtl rendering.  It seems like OTRS needs to two timediffs tracked, one for the server-UTC diff and one for the client-UTC diff (or just make sure that the ticket object is pure UTC and only the DTL does conversions).<br>
<br>Keeping to the point, has anyone else investigated this and can share insights?  Were there any reasons UTC was initially avoided?<br><br>I&#39;ll admit I am running this on SQL Server,  IIS, and ActiveState Perl - any of  which might cause my results to differ from the &quot;norm&quot;.<br>
<br>Regards,<br>Hugh<br>