Issues After Upgrading to 4.4

Hi All,

After Upgrading to 4.4 I noticed that values for Custom DateTime Fields
entered by non root users is being considered as UTC irrespective of what
timezone has been set in RT_SIteConfig. For en example, with Asia/Dubai
(UTC +4) as a time zone, when I select 6:00 PM and create the ticket, it
gets displayed as 10:00PM. However there is no such issues when logged in
as root.

Appreciate your immediate support on this.

Thank you
Kind Regards,
Jeet

Hi All,

Did anyone face this issue ?

Kind Regards,
Satyajeet Singh
Dubai: +971 551185369
India: +91 9911547664On 11 February 2016 at 21:45, Satyajeet Singh jeet.0733@gmail.com wrote:

Hi All,

After Upgrading to 4.4 I noticed that values for Custom DateTime Fields
entered by non root users is being considered as UTC irrespective of what
timezone has been set in RT_SIteConfig. For en example, with Asia/Dubai
(UTC +4) as a time zone, when I select 6:00 PM and create the ticket, it
gets displayed as 10:00PM. However there is no such issues when logged in
as root.

Appreciate your immediate support on this.

Thank you

Kind Regards,
Jeet

Hi Sean,

Thanks for replying, I checked that, its system default for all the
unprivileged users and it is set as Asia/Dubai on OS and in RT_SiteConfig.pmOn 16 February 2016 at 22:05, Sean Ellefson scellef@pdx.edu wrote:

HI Satyajeet,

Have you checked the locale settings under your user options? There’s an
option for listing all dates under GMT next to others around your timezone.

On Sat, Feb 13, 2016 at 9:55 PM, Satyajeet Singh jeet.0733@gmail.com wrote:

Hi All,

Did anyone face this issue ?


Kind Regards,
Satyajeet Singh
Dubai: +971 551185369
India: +91 9911547664

On 11 February 2016 at 21:45, Satyajeet Singh jeet.0733@gmail.com wrote:

Hi All,

After Upgrading to 4.4 I noticed that values for Custom DateTime Fields
entered by non root users is being considered as UTC irrespective of what
timezone has been set in RT_SIteConfig. For en example, with Asia/Dubai
(UTC +4) as a time zone, when I select 6:00 PM and create the ticket, it
gets displayed as 10:00PM. However there is no such issues when logged in
as root.

Appreciate your immediate support on this.

Thank you

Kind Regards,
Jeet


RT 4.4 and RTIR Training Sessions (
http://bestpractical.com/services/training.html)

  • Hamburg Germany - March 14 & 15, 2016
  • Washington DC - May 23 & 24, 2016

Sean Ellefson
Linux Systems Administrator - Computer Infrastructure Services
Office of Information Technologies
Portland State University
Phone: 503-725-9157
scellef@pdx.edu

Dear Sean,

Did you manage to find any solution for this. Apologies, but we are
planning t update to 4.4 for new features but not able to do it due to this
issue.

Thanks a lot for your help.

Kind Regards,
Satyajeet Singh
Dubai: +971 551185369
India: +91 9911547664On 17 February 2016 at 09:35, Satyajeet Singh jeet.0733@gmail.com wrote:

Hi Sean,

Thanks for replying, I checked that, its system default for all the
unprivileged users and it is set as Asia/Dubai on OS and in RT_SiteConfig.pm

On 16 February 2016 at 22:05, Sean Ellefson scellef@pdx.edu wrote:

HI Satyajeet,

Have you checked the locale settings under your user options? There’s an
option for listing all dates under GMT next to others around your timezone.

On Sat, Feb 13, 2016 at 9:55 PM, Satyajeet Singh jeet.0733@gmail.com wrote:

Hi All,

Did anyone face this issue ?


Kind Regards,
Satyajeet Singh
Dubai: +971 551185369
India: +91 9911547664

On 11 February 2016 at 21:45, Satyajeet Singh jeet.0733@gmail.com wrote:

Hi All,

After Upgrading to 4.4 I noticed that values for Custom DateTime Fields
entered by non root users is being considered as UTC irrespective of what
timezone has been set in RT_SIteConfig. For en example, with Asia/Dubai
(UTC +4) as a time zone, when I select 6:00 PM and create the ticket, it
gets displayed as 10:00PM. However there is no such issues when logged in
as root.

Appreciate your immediate support on this.

Thank you

Kind Regards,
Jeet


RT 4.4 and RTIR Training Sessions (
http://bestpractical.com/services/training.html)

  • Hamburg Germany - March 14 & 15, 2016
  • Washington DC - May 23 & 24, 2016

Sean Ellefson
Linux Systems Administrator - Computer Infrastructure Services
Office of Information Technologies
Portland State University
Phone: 503-725-9157
scellef@pdx.edu

Hi,

if you use mod_perl, then the docs have the answer:
https://www.bestpractical.com/docs/rt/4.2/web_deployment.html#mod_perl-2.xx

ChrisAm 11.02.2016 um 18:45 schrieb Satyajeet Singh:

Hi All,

After Upgrading to 4.4 I noticed that values for Custom DateTime Fields
entered by non root users is being considered as UTC irrespective of
what timezone has been set in RT_SIteConfig. For en example, with
Asia/Dubai (UTC +4) as a time zone, when I select 6:00 PM and create the
ticket, it gets displayed as 10:00PM. However there is no such issues
when logged in as root.

HI Chris,

I already tried the solution given at this link but with no success, I also
think that this is not the same issue, because for root user it is working
fine but for others its assuming that the time entered in custom DateTime
field is in GMT, hence rt is converting it to +4:00 to match the actual
timezone.

Kind Regards,
Satyajeet Singh
Dubai: +971 551185369
India: +91 9911547664On 3 March 2016 at 11:55, Christian Loos cloos@netcologne.de wrote:

Hi,

if you use mod_perl, then the docs have the answer:
Web deployment - RT 4.2.17 Documentation - Best Practical

Chris

Am 11.02.2016 um 18:45 schrieb Satyajeet Singh:

Hi All,

After Upgrading to 4.4 I noticed that values for Custom DateTime Fields
entered by non root users is being considered as UTC irrespective of
what timezone has been set in RT_SIteConfig. For en example, with
Asia/Dubai (UTC +4) as a time zone, when I select 6:00 PM and create the
ticket, it gets displayed as 10:00PM. However there is no such issues
when logged in as root.