Select a group that will receive email notifications when a script (e.g. Post Function or Script Listener) fails to execute successfully.

The default value is the 'site-admins' group.

Additionally, you can chose whether the Assignee and the Reporter of an issue should also be notified by email if a script fails to execute successfully on a particular issue.

You can configure particular user groups in order that they will not receive a notification of a failed script execution if they are the Assignee or Reporter of the issue that triggered the script.

The default value is no groups.

This is useful if you only want some Assignees or Reporters to receive email notifications of script errors.

As described in the Limitations, the maximum amount of code that can be stored in each of the three features Script Listeners, Escalation Services and Scheduled Jobs is 32KB as they are stored within Jira.

We have an alternative solution which does not impose a limit on the amount of code you can store. However, your scripts will be stored externally from your Jira instance in ScriptRunner Cloud Storage, and will no longer be part of any Jira exports (so your scripts cannot be automatically migrated between Jira instances). Additionally it is not possible to migrate your scripts back into Jira’s storage.

If you require more storage, feel free to create a support request.

You can set the timezone in which your scripts will execute here. This is the value used to set the Java TimeZone.

The default value is 'UTC'.

This setting toggles whether the ScriptRunner Enhanced Search page is available to users.

When this setting is enabled, if you view an issue ScriptRunner will check for a short period of time in case any other users update the issue, and will display a message if they do. This helps notify you of changes made asynchronously by Post Functions and Script Listeners.

Specifies how often ScriptRunner synchronises your filters. The default interval is five minutes. The maximum allowed interval is an hour. We recommend you to use the default value, unless you notice that filter synchronising makes too many requests to your JIRA instance and causes a performance problem.

Every X minute, ScriptRunner will check if something has changed in your JIRA issues or someone has changed the ScriptRunner add-on settings recently. If check is positive, 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.