Function Name Differences

ScriptRunner for Jira Server/DC and Cloud function name differences are outlined below:

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.