Settings

This section helps you understand how to set up your ScriptRunner for Jira Cloud configurations. You can use the Settings page to configure your preferences and save when complete.

Click the Settings button on the top right corner of your page, or from the ScriptRunner menu, and the options shown below are displayed:

General

You can choose the time zone in which your script will execute by selecting your region from the Scripts Time Zone drop-down list. This is the value used to set the Java TimeZone.

The default value is 'UTC'.

It is important to note that since the Java 8 release, you should avoid using the Date class and use the Calendar, Instant, and Zoned Time classes.

You can find some useful examples in this blog post.

Notifications

Notifications group

If a script fails to execute successfully, you can send a group email to notify those concerned. For example, if a Post Function or Script Listener associated with an issue-related event fails to run, an email is automatically sent to the designated notification group.

To do so, select the relevant Notifications Group from the drop-down list. The default value is the 'site-admins' group.

Notify assignee and reporter

In addition to the group notification, you can activate the Notify Assignee and Reporter option to send an email notification to the Assignee and Reporter of the failed script.

Exclude groups

Within the notification settings, you can also use the Exclude Groups setting to ensure the assignee or reporter of a failed script does not receive an email notification of that issue. To do so, select the user group associated with the Assignee and Reporter from the drop-down list.

The default value is 'no groups'.

Issue polling notifications

Enabling Issue Polling Notifications means you are notified of changes made asynchronously by Post Functions and Script Listeners for issues you have viewed.

ScriptRunner checks for updates on the issues made by any other users for a short period of time and displays a notification message when updates occur.

Enhanced Search feature

You can enable the use of the ScriptRunner Enhanced Search feature by activating this option. This provides you with search capabilities in Jira Cloud using advanced JQL functions that are not available by default in Jira Cloud.

Using ScriptRunner JQL functions removes the need to learn the Atlassian SDK and provides you with a simple method for writing your own JQL functions.

Filter sync interval period

When the Enhanced Search feature has been turned on, this setting checks every 'X' minutes for changes in your Jira issues or if another user has recently changed the ScriptRunner add-on settings. If changes have occurred, then filters are synced with the changes made to the issues in your Jira instance. Filters are always run with the same set of permissions as the user who created the filter.

You can select the Filter Sync Interval Period from the options available in the drop-down list to specify how often ScriptRunner synchronizes your filters. The maximum interval period allowed is one hour. However, the default interval of five minutes is recommended.

You should adjust the default interval period if you notice that filter synchronizing makes too many requests to your Jira instance and causes a performance problem. You can refer to our filter sync performance documentation for further information.

ScriptRunner AI

Your ScriptRunner for Jira Cloud organization's administrator can enable the Behaviours Bot for your instance. This feature is turned off by default.

The Bot is an AI-powered script generation assistant built into ScriptRunner for Jira Cloud. It converts natural, everyday language instructions into ready-to-use Behaviours scripts. You can utlize the functionality of the Behaviours Bot to create new Behaviours scripts, or modify, refine, and improve existing ones.

Admin issues for the Behaviours Bot

In order to access and activate the Behaviours Bot setting, you must belong to the org-admins or site-admins groups.