All scheduled issues firing 2 hours late

[loubal]

All scheduled issues being sent 2 hours late.

[Łukasz Modzelewski]

Trigger is set based on JIRA server time, but upcoming issues are displayed based on User time zone.

See attached screenshots showing triggers:

01 - without any default user time set - just server time.

02 - with modified "Default user time zone" there is a note that this is UTC Time Zone.

03 - trigger set with UTC Time Zone, upcoming issues displayed in users Time Zone

Let us know if this explanation solved your problem

Best regards,

Łukasz

[loubal]

Hi,

Pretty sure I was in CET/CEST when I set the triggers, as seen below:

Probably this happened due to recent DST in Europe?

[Łukasz Modzelewski]

This could be the case, but still it looks a bit strange. If user is in different time zone than server there is an information in parenthesis about triggers time zone eg. (CET TIME ZONE), but in your case I see that there is no indication of different time zone.

check attached screenshots:

Setting up trigger.

Admin in different than server time zone.

User "lppa" in same as server time zone.

1. When did you noticed this behavior? was it after time change or after upgrading to latest 5.0.0 version?

2. Please also check if the date of the created issue in JIRA is correct - maybe the problem is only with displayed date.

3. You could also send us logs (at [e-mail] ) maybe we could find something there indicating time shift.

Link to documentation where to find log file:

https://confluence.atlassian.com/adminjiraserver073/logging-and-profiling-861253813.html