Confluence has been updated to version 6.15.9

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

titlejira on-premise

This page describes how you can store advanced groovy scripts outside the Sync Rules processors.


CSS Stylesheet
code {
    color: #c7254e;
    background-color: #f9f2f4;
    border-radius: 5px;
    font-weight: bold;
    padding: 3px 3px;

In this section

Table of Contents
excludeIn this section


Advanced synchronization scripts usually contain a huge number of code lines. Storing these scripts in the Sync Rules make it hard to maintain.



The scripts directory must have permissions to write and read directories/files.

Where to set up scripts


Custom scripts can only be deployed on Jira Server/Datacenter and nodes which are deployed through the docker deployment approach.

Jira Server


Jira Datacenter


Docker based


There could be one of the following values instead of <nodename>:

  • snownode for Exalate for ServiceNow.

  • adnode for Exalate for Azure DevOps.

  • hpqcnode for Exalate for HP ALM/QC.

Jira Cloud

Jira Cloud, just as any other cloud node, supports a set of specific scripts. Custom scripts cannot be deployed in this environment.

Check out List of external scripts for Jira Cloud for more information.

Available external scripts

Exalate documentation includes a lot of example scripts containing approaches on how to implement various use cases.  Please note that many of these scripts are used only for example purposes. 


Excerpt Include
List of external scripts for Jira Serveron-premise
List of external scripts for Jira Serveron-premise

What's next

Check an example of how you can add an external script

Set up advanced scripting environment

Externalize your existing scripts