Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Pentaho Scheduler always takes the browser time zone and ignores the time zone from the drop down menu on the Pentaho Server

Description

The Pentaho Server is hosted in a different time zone. The Pentaho users are accessing it from a different timezone. When they shedule a KTR file through the PUC, they select the date, time and frequency of run on the scheduler based on the time zone from drop down menu on the scheduling page. However the timezone chosen from the drop down menu gets completely ignored and instead the schedule seems to be based on the local time zone of the user / browser from where the page was accessed.

Environment

None

Test Cases

None

Steps to Reproduce

  1. Pentaho Server is hosted and running in a particular time zone e.g., GMT

  1. Access the Pentaho User Console from a brwoser located in a different timezone e.g., IST

  1. Navigate to Schedules -> Manage Schedulespage and choose

  • Set a Recurrence for example Seconds

  • Set a Start Time for example 10:00AM Choose a Time Zone from the drop down menu for example British Summer Time (UTC+0100)

  • Key in a Recurrence Pattern say every 30 seconds

  • Provide a Range of Occurence starting today. Click Finish

  1. The User expects the KTR file to be executed every 30 seconds starting 10:00AM British Summer Time (BST). But instead the schedule takes effect at 10:00AM IST. It appears the browser's local time zone overrides the time zone chosen from the drop down menu viz., British Summer Time (BST)

  1. When the User navigate to the Kettle Status Page, the time displayed after execution of the KTR is the time based on BST and not IST

  1. When a different User from a different time zone views the same schedules and times through PUC, the times displayed are once again based on local time zone of that user / browser

Please also refer to ESR-7364

Workaround

None

Activity

Show:

Details

Assignee

Reporter

Edit Screen Preamble

<div class="notify info" style="margin-bottom: 10px;">
If you are a Pentaho customer, please use the <a href="http://support.pentaho.com">Customer Support portal</a> to log issues.
<p />
This system is used for logging bugs and enhancement requests only. Please use our <a href="https://community.pentaho.com">community at https://community.pentaho.com</a> if you have questions, configuration issues, or have an issue with a marketplace plugin as Pentaho does not support marketplace plugins unless written by Pentaho.
<p />
Lastly, when creating a bug, please provide as much detail as possible. To prevent unnecessary delays in reviewing your issue, please attach complete server logs, SQL/MDX logs where applicable, schemas, etc. Also, screen-shots and screen-cams are especially helpful in demonstrating the issue.
<p />
Thank-you so much,<br />
The Pentaho Team
</div>

Notice

<div class="notify info" style="margin-bottom: 10px;">
When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.
</div>

Compliance Product Line

Pentaho

Story Points

Priority

Created March 24, 2022 at 4:39 PM
Updated February 8, 2023 at 1:34 AM