Several limitations are applied to scripts when they run, as detailed below. The limits should be more than sufficient for most scripts and are designed to catch erroneous scripts.
There is a limit of 240 seconds for script executions. After running for 240 seconds, the logs will be collected, and the code will be terminated. Any logs from the first 240 seconds of execution will be logged on the Script Logs page.
There is a limit of 30 seconds for each call made to the API. We impose these timeouts to prevent scripts/API calls from running for a long time period and impacting the performance of the Jira Cloud infrastructure provided by Atlassian. We cannot change the timeout for each API call.
There is a limit of 10MB on how much data you can send in a REST API request to Jira or Confluence. This is likely only to impact uploading attachments to Jira or Confluence. The REST API call may fail with a 500 or 413 HTTP response.
There is a JVM limitation that relates to the size of methods within scripts. This is imposed by Java rather than ScriptRunner or Jira, as documented in the Atlassian KB. A single method can consist of up to 65536 bytes of bytecodes before the JVM limit returns the error shown below:
General error during class generation: Method code too large
Scripts in ScriptRunner Cloud Storage
Our scripts are stored externally from your Jira instance in ScriptRunner Cloud Storage. The scripts are not part of any Jira exports, meaning that they cannot be automatically migrated between Jira Cloud instances. Currently, it is not possible to migrate your scripts back into Jira Cloud’s storage. If you require a larger amount of storage you can create a support request.
Please note that we store Behaviours using the UI Modifications API, so at a maximum, you can create 3000 Behaviours. However, a context (combination of project, issue type and view that the behaviour is executed on) can only be used for 100 behaviours.
Jira back-ups and ScriptRunner data
As scripts are stored in our AWS hosting infrastructure and NOT stored within Jira (with the exception of Workflow Post Functions), then you should be aware that if a Jira backup is performed, you are not backing up any links to the ScriptRunner Cloud data.
Unfortunately, the instance URL is irrelevant. So if you perform a site import or a restore of a backup, even with the same URL, the ScriptRunner Cloud data won't necessarily reappear. In some cases, the opposite is true.
You cannot import external libraries as this is not supported. Whilst you can import packages into your scripts in the Script Console, Script Events and Post-Functions, you can only import from the standard Java 11 classes and the following libraries:
ScriptRunner is built to use the UniRest library as shown in the above list for making REST API calls. This allows you to make a REST API callwith BasicAuthentication using a structure similar to the one outlined below. Remember to make sure you are doing this over HTTPS.
def result = get('/rest/project-templates/1.0/createshared/10005') .basicAuth('firstname.lastname@example.org', 'XXXX') // enter here your username and API token. .asObject(Map) .body