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 120 seconds for script executions. After running for 120 seconds, the logs will be collected, and the code will be terminated. Any logs from the first 120 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, but we can increase the limit of the script execution to a maximum of 240 seconds. If you find you are receiving a timeout error when trying to execute your scripts, please raise a support request

Method Size

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

Currently, the maximum amount of code that can be stored within Jira Cloud across all ScriptRunner features is 32KB per feature. Note that the exception is the Behaviours feature, which has a limit of 3MB. So, if one Script Listener contains 30KB of code, then all your other Script Listeners must only contain 2KB of code between them.

The same maximum storage limit applies to the Escalation Services and Scheduled Jobs features.

Please note that our scripts are stored externally from your Jira instance in ScriptRunner Cloud Storage. Our 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.

Package imports

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:

  • org.codehaus.groovy:groovy:2.5.14
  • org.codehaus.groovy:groovy-dateutil:2.5.14
  • org.codehaus.groovy:groovy-datetime:2.5.14
  • org.codehaus.groovy:groovy-nio:2.5.14
  • org.codehaus.groovy:groovy-json:2.5.14
  • org.codehaus.groovy:groovy-jsr223:2.5.14
  • org.codehaus.groovy:groovy-templates:2.5.14
  • org.codehaus.groovy:groovy-xml:2.5.14
  • org.codehaus.groovy:groovy-sql:2.5.14
  • com.fasterxml.jackson.core:jackson-core:2.12.0
  • com.fasterxml.jackson.core:jackson-annotations:2.12.0
  • com.fasterxml.jackson.core:jackson-databind:
  • io.github.openunirest:unirest-java:2.2.10
  • org.apache.httpcomponents:httpclient:4.5.13
  • org.apache.httpcomponents:httpcore:4.5.13
  • org.apache.httpcomponents:httpasyncclient:4.1.4
  • org.apache.httpcomponents:httpcore-nio:4.4.10
  • org.apache.httpcomponents:httpmime:4.5.13
  • org.slf4j:slf4j-api:1.7.30
  • org.slf4j:slf4j-log4j12:1.7.30
  • org.slf4j:jcl-over-slf4j:1.7.30
  • log4j:log4j:1.2.17
  • org.immutables:builder:2.8.8
  • io.jsonwebtoken:jjwt:0.9.1
  • org.postgresql:postgresql:42.2.19
  • mysql:mysql-connector-java:8.0.23
  • org.jsoup:jsoup:1.14.3

UniRest Library

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('', 'XXXX') // enter here your username and API token. .asObject(Map) .body
On this page