| Info | ||
|---|---|---|
| ||
This routine is available starting with Power Scripts for Jira 3.0.8. This routine is available for Jira server and cloud deployment options. Starting with version 4.8.0.10 of Power Scripts an optional param will be available that will give the possibility to assume an user when executing the script. |
Syntax
runJobByCron(silFile, args, cronExpr)
...
Parameter name | Type | Required | Description |
|---|---|---|---|
silFile | string | Yes | The sil file name. |
| args | array string | Yes | The list of the arguments of the job. |
| cronExpr | string | Yes | The cron expression |
| user | string | No | The user which will be used to run the script. |
| Note | ||
|---|---|---|
| ||
You can find more details about using the cron expression according to the used API at www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger |
...
| Code Block |
|---|
string issueKey = argv[1]; |
| Warning | ||
|---|---|---|
| ||
This routine doesn't assume any user when executed because of the nature of this action(the execution of the script can be scheduled at any point in time and that cannot guarantee the user is authenticated). 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. |
See also
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...