Skip to end of metadata
Go to start of metadata

Contents

SIL Scheduler Page

You can access the SIL Scheduler page from Administration > SIL Scheduler.

Scheduler page columns

ColumnDescription
ScriptFull path to the script and the arguments if they exist
ScheduleEither the interval on which the script should run or the CRON expression interpreted
Next RunDate and time of the next run
Runs asUser to impersonate when running the script
OperationsPossible operations to do with a scheduler (delete, in our case)

Managing SIL™ Scheduler

The SIL™ Scheduler feature enables you to run SIL™ scripts after a valid Jira interval or using a CRON expression.

Starting with version 4.0.0 of Power Scripts™, the jobs are persistent that is they are kept alive towards Jira restarts. You can read about scheduling jobs here: Scheduling routines. This mechanism uses the same scheduling engine, thus the same notes apply.


Each scheduled job has the following properties:

  • Scheduler type - either interval or CRON expression
  • Schedule - valid Jira interval or a CRON expression
  • Repeatable - if you use a Jira interval, you can define whether the job should repeat at the specified interval
  • Script - SIL Script that will run using the schedule that you define
  • Arguments - job arguments
  • Run script as - if specified, the script will run as if by this user



To schedule a CRON job, change the type to "CRON" and enter a valid schedule (Quarts CRON expression).

The Quarts Cron expressions also considers the seconds, unlike the traditional Cron expressions:


SIL Scheduler: Sec Min Hour Day Month Day of Week

Traditional Cron: Min Hour Day Month Day of Week

Info

To edit the actual scripts, use the SIL™ Manager.

After saving the added job, a new entry is added to the table on the Administration page.

No user provided

Please keep in mind that if no value is provided in the Run this script as textfield, the script will run with no user. Therefore, the script will NOT have the required permissions to interact with Jira tickets, unless the project allows for anonymous access or the script explicitly calls out the user to use within in the script using the runAs routine.

It is highly recommended to provide a user to the scheduled job when interacting with Jira tickets.

We have removed standard services from Power Scripts™ for Jira v4.0 - all your scripts will be migrated to the scheduler, because it provides a more flexible mechanism. 

See also