Recurring jobs triggering at an unexpected time

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

When a user's time zone is set to be different from the server time zone (App, DB and BG servers are all on the same time zone) under Account Settings, and schedules a recurring job using Crontab, the resulting job schedule is set to the wrong time.

The time specified in the Crontab text seems to be on server time, and not user's time zone setting.

This issue is consistent when hour is specified in the Crontab text. Meaning "0 11 * * *" will give you the incorrect time; while "0 * * * *" will give you the correct time

Steps to Reproduce:

Prerequisites: CA PPM servers (all App, DB, BG servers) have time zone set to the same time zone, say US Pacific Time

1. Log in to the application and navigate to Account Settings
2. Set time zone to US Pacific Time
3. Schedule a recurring job by filling in the following:
   Click Submit on the Job Properties page to land on the Scheduled Jobs page.
   1. Uncheck the box for 'Immediately'
   2. Check the box for 'Scheduled'
   3. Set Start Date to the next day (or any other day)
   4. Set Start Time to any time
   5. Click on 'Set Recurrence'
   6. Check the radio button for Crontab, enter "0 11 * * *" to the text box, click Submit
4. The job is scheduled to 11AM the next day as expected.
5. Go to Account Settings, change the time zone to a different one, say US Central Time.
6. Repeat the steps for #3 above.

Expected Result: The job is scheduled to 11:00 AM the next day as expected.

Actual Result: The job is scheduled to 1:00 PM the next day.

Environment

Any Release

Resolution

This is working as designed, Crontab always picks up the server time.