Actions
Bug #14378
closedWrong timezone in start_at field
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
When tasks gets created but is not run yet, you can see that start_at is set without respecting the timezone. On my system it was shifted by 2 hours from started_at. Once executor runs the task, time gets updated correctly. Tested with 0.7.15
Updated by Marek Hulán about 8 years ago
- Related to Bug #14377: All tasks are displayed with execution type delayed added
Updated by Ivan Necas over 6 years ago
- Is duplicate of Bug #21263: Time zone changes in Schedule future execution & Set up recurring execution added
Actions