Migrate from ScriptRunner for Jira Server to Cloud

You can migrate from ScriptRunner for Jira Server/DC to Cloud either:

We recommend you use the Cloud Migration Assistant when migrating an instance with ScriptRunner from Server to Cloud.

Be aware that any migration from Server to Cloud (manual or through the Atlassian Cloud Migration Assistant) will require rewriting scripts.

Migration Process

Whether you are using the Cloud Migration Assistant or manually migrating, you must follow these steps:

Features Supported by Jira Cloud Migration Assistant

The following features are migrated from Jira Server to Jira Cloud when using the Atlassian Cloud Migration Assistant:

  • Custom Script Field
  • Custom Script Listener
  • Custom Jobs
    • Escalation Services
  • JQL Functions
    • epicsOf
    • nextSprint
    • linkedIssuesOfRecursive
    • subtasksOf
    • projectMatch
    • previousSprint
    • parentsOf
    • dateCompare
    • componentMatch
    • linkedIssuesOf
    • issueFieldMatch
    • issuesInEpics
    • linkedIssuesOfRecursiveLimited
    • issueFieldExactMatch
    • versionMatch
  • Workflow Functions

hasLinks function

Server filters that use the hasLinks function will not work in Cloud; they will need to be manually updated to use the native JQL keyword issueLinkType instead.

The table below outlines the differences between the Server and Cloud function names and provides guidance on how these fields may be mapped together when migrating Workflow functions. 

You should note the following points when using the Atlassian Cloud Migration Assistant:

  • If you have already migrated a project with the assistant and want to re-migrate it again, then you must delete the project and associated workflows/workflow scheme in order for the workflow rules to be migrated. Jira does not delete these when a project is deleted.
  • Any scripts commented out, due to the fact that the APIs are different between Server and Cloud, will need to be rewritten.

  • Conditions and Validators use the Jira Expression language.
  • Built-in script conditions or validators migrated from Jira Server/Data Centre are not supported and will display in ScriptRunner for Jira Cloud as blank validators or conditions. Therefore, once the migration is performed, these will need to be deleted.

Jira Server and Cloud Function Name Differences

Server Function Name:

Cloud Function Name:

Incompatible Fields that should be discarded:

Add/remove from sprint [ScriptRunner]

Add/remove from sprint

  • Return user to Execute As - In Cloud, users can run as the Add-on or initiating user only and cannot choose a specific user to run the post function.

Assign to first member of role [ScriptRunner]

Assign Issue

  • Include Reporter

  • Include Assignee

  • Force Asignee

Clones an issue, and links [ScriptRunner]

Clone Issue

  • Fields to copy

  • Copy Comments

  • Copy Subtasks

  • As User - In Cloud, users can run as the Add-on or initiating user only and cannot choose a specific user to run the post function.

Create a sub-task [ScriptRunner]

Create Subtask

  • Fields to copy

  • As User - In Cloud, users can run as the Add-on or initiating user only and cannot choose a specific user to run the post function.

Fast-track transition an issue [ScriptRunner]

Fast-track transition issue

  • Transition Options

Transition parent when all subtasks are resolved [ScriptRunner]

Transition Parent Issue

  • No incompatible fields.

Custom script post-function [ScriptRunner]

Run Script

  • No incompatible fields.

Custom script validator [ScriptRunner]

ScriptRunner Script Validator

  • Test Against - Used for testing scripts when creating or editing validatiors only, so can be safely discarded.

Custom script condition [ScriptRunner]

ScriptRunner Script Condiion

  • Test Against - Used for testing scripts when creating or editing validatiors only, so can be safely discarded.

It's worth noting that any fields that could not be mapped, such as, when an item is referenced by ID, will be mentioned in a comment within the Conditions box of the workflow rule.

Once migrated, these features are deactivated so you can make them Cloud compatible before reactivating.



On this page