Getting Started

Features

Configuration

This page allows you to configure your settings for the ScriptRunner for Confluence add-on.

The following settings are configurable:

Notifications Group

Select a group that will receive email notifications when a script (e.g. Script Listeners) 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.

Exclude Groups

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.

Scripts Time Zone

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'.

Note

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.

Store Scripts in ScriptRunner Cloud Storage

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

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 Confluence instance in ScriptRunner Cloud Storage, and will no longer be part of any Confluence exports (so your scripts cannot be automatically migrated between Confluence instances). Additionally it is not possible to migrate your scripts back into Confluence’s storage.

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

Built-in Scripts Space Admin Permission

Confluence Administrators have control of space admin?s use of the features in Advanced Space Functionality and can revoke permissions for specific groups of users and spaces.

It is also possible to disable space admin Built-in Scripts for the entire Confluence instance.

NB - By default all space admins will have access to advanced space functionality.

Note

To find out more about assigning space admin permissions, take a look at Atlassian’s documentation.

How to use it

Table View
  • Add the name of the group(s) or the space(s) that you wish to disable the Advanced Space Functionality.

  • To disable the feature across all spaces, please tick the necessary box.