Incorrect timezone in date display

[Andrew Black]

I'm not certain if this is actually a bug in The Scheduler or JIRA (7.4.2), but I'm filing it here as this is where the problem was observed.

The environment where my JIRA instance runs ins a mis-mash of timezones. The host where the instance resides utilizes UTC for it's time clock, while the default user timezone is America/Los Angeles (PDT).

When interacting with The Scheduler, all times are displayed in UTC (host timezone), but the JIRA scheduling facility utilizes PDT (default user timezone) for task scheduling. I glanced at the JIRA documentation, but couldn't find anything to suggest what the expected behavior was.

[Dominik M.]

Dear Andrew,

I'll do my best to replicate the environment and let you know what can be done.

Can you also specify what The Scheduler add-on exact version do you use?

Regards, Dominik

[Andrew Black]

Greetings Dominik.

We are running version 5.0.6 of The Scheduler.

--Andrew Black

[Dominik M.]

Dear Andrew,

The issue was replicated - it exists and it fact this creates a lot of confusion. It was agreed that future versions of the add-on should be redesigned to present time of scheduled and executed issues in a standarized manner, so there won't be a situation when e.g. anyone who plans and creates an issue according to the UTC time zone (JIRA host time zone) will see scheduled issue execution time in PDT (time set only for his/her JIRA profile). This should avoid confusion also for people located in different time zones, as they are not sure when exactly such issue was created (when execution time occurred).

To get notified about new versions you can use 'Start watching" option on this website: https://marketplace.atlassian.com/plugins/pl.com.tt.jira.plugin.theschedulerpro/server/overview

Regards, Dominik

[Andrew Black]

One other wrinkle to be aware of when implementing a fix is that the execution timezone is the default user timezone, and not the user's selected timezone. This is why I stated I wasn't certain if it was a JIRA bug or a bug in The Scheduler.

To verify this, you will need to set your user timezone to something other than the default (America/New York in my case). After doing so, compare the cron entries in the system Scheduler details (/secure/admin/SchedulerAdmin.jspa) with those in the Manage Scheduled Issues area (/secure/ManageScheduledIssues!default.jspa). You will find that the cron entries are identical.

When I was initially drafting the bug report, I had mentioned that my user timezone wasn't the default user timezone. I had eliminated this comment in an effort to remove extraneous details, but perhaps I should have left it.

--Andrew Black

[Łukasz Modzelewski]

Hi Andrew,

We are currently working on this issue, it should be fixed in next release 5.1.1 - I'll close the ticket, when it will be available on Marketplace.

Cheers,

Łukasz

[Łukasz Modzelewski]

Hi Andrew,

Fixed version 5.1.1 is now available on Marketplace.

Cheers,

Łukasz