Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Major |
| Complexity | Unknown |
| Component | User - Project - Scheduled Jobs |
| Version | 2.0 |
Currently, if a scheduled job is created in PST to run at 10 am daily, then after daylight savings time kicks in, the job runs at 11 am daily.
Desired result: The job should continue running at 10 am daily, post DST.
Reference discussion: https://www.aquaclusters.com/app/home/project/public/aquadatastudio/discussion/General+Discussions/post/34/Scheduled+Jobs+in+ADServer+running+an+hour+late
|
|
166 KB
|
|
68 KB
Since we don't know the time zone of any jobs that were created prior to this release, we'll need to set the time zone to GMT for all existing jobs.
Also, create a special migration script for Brian so that we can convert all his existing jobs to his correct time zone (Eastern).
1. For recurring jobs created in V1.0 and migrated to 2.0, I fast forwarded to Nov 4 at which day light savings occur.
Edited and Saved the job and now displays correct time with no 1 hour delay
2. Created jobs in v2 and fast forwarded and jobs are scheduled at correct time - no delay
1. For recurring jobs created in V1.0 and migrated to 2.0, I fast forwarded to Nov 4 at which day light savings occur.
Edited and Saved the job and now displays correct time with no 1 hour delay
2. Created jobs in v2 and fast forwarded and jobs are scheduled at correct time - no delay
Issue #2837 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
Since we don't know the time zone of any jobs that were created prior to this release, we'll need to set the time zone to GMT for all existing jobs.
Also, create a special migration script for Brian so that we can convert all his existing jobs to his correct time zone (Eastern).