Feature Parity and Script Alternatives

See which ScriptRunner for Jira Data Center features are available in Isolated Cloud, and any script or native Jira alternatives.

ScriptRunner for Jira Isolated Cloud doesn't have the same feature set as ScriptRunner for Jira Data Center. The following tables show the parity of each Data Center feature and any alternatives, such as a script example, a custom script you can write, or a native Jira feature.

The tables also list Data Center features that aren't supported or aren't applicable in Isolated Cloud, so you can make an informed decision before you migrate.

CAUTION: Jira REST API and UI Modifications API

The varying parities between Isolated Cloud and Data Center are due to limitations in the Jira REST API and the UI Modifications API, which ScriptRunner relies on to provide certain functionality. Some features cannot be included in the Isolated Cloud feature set due to architectural limitations of the Isolated Cloud platform. There are also some general limitations within ScriptRunner for Jira Isolated Cloud, such as script execution timeouts and script storage, which we recommend reviewing.


Key	Definition	Meaning
✓	Full parity	This feature is available in ScriptRunner for Jira Isolated Cloud. Some platform-specific limitations may apply.
◐	Partial parity	Core functionality is available, but some capabilities differ from the Data Center version.
💡	Scripting or native solution	No direct feature equivalent, but you can achieve similar results using custom scripts or native Jira functionality.
✗	No parity	Not available in Isolated Cloud due to platform restrictions or architectural differences.
N/A	Not applicable	Not relevant or not required in the Isolated Cloud environment (for example, relies on concepts that only exist on DC).

Behaviours

Parity summary

This feature is known as Field Behaviours in ScriptRunner for Jira Isolated Cloud. While this feature has certain limitations in the Isolated Cloud environment (detailed in the table below), you can still implement various common use cases, such as:

Set the default value for the summary field
Set the description field using markdown
Change a field's display name

See our Field Behaviours Examples for a complete collection of pre-written scripts that address common use cases.

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Behaviours	✓	Atlassian created an API called UI Modifications on the Forge platform, which made it possible for ScriptRunner to build Behaviours. As more capabilities become available in the UI Modifications API, more functionality can be built in ScriptRunner's Behaviours feature. Behaviours is a key focus within ScriptRunner's product development roadmap. We are actively enhancing this feature by integrating new capabilities as Atlassian releases them. Notable differences for field behaviours on Isolated Cloud: You can apply Behaviours to the Create, Work Item, and Transition views (Create, View/Edit, Transition view types) of a Jira Work Item. Refer to Supported Fields and Products for Field Behaviours for details. There are certain limitations set by Atlassian. See our Field Behaviour Limitations section for more details. Behaviours may be applied to certain supported fields only, as not all fields are currently supported in all available views. Notable parity for Behaviours on Cloud: ✓ Compatible with Jira Software and JSM. ✓ Company and team-managed projects are supported. ✓ Support for over 30 system and custom field types across all three Create, Issue, and Transition views (Create, View/Edit, Transition view types). See our field behaviours page for more details.

Built-In Scripts

Parity summary

ScriptRunner for Jira Isolated Cloud offers a limited selection of built-in scripts compared to the Data Center version. However, alternative scripts that can be executed through the Script Console are available in Cloud. Where applicable, links to these script alternatives are provided in the table below.

See our Script Console Examples for a complete collection of pre-written scripts that can be run from the Script Console.

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Bulk Copy SLA Configuration	N/A	This is not applicable in the Jira Isolated Cloud environment. SLA configurations are managed through Jira Service Management's native interface in Cloud. The REST API doesn't provide endpoints for bulk SLA configuration operations, and this is considered an administrative setup task rather than a scripting use case.
Bulk Fix Resolution	💡	The Bulk work item resolutions script is available in-app from the Example scripts modal in the script console. You can customize this script to meet your requirements.
Bulk Import Custom Fields	💡	You can achieve the same result by writing your own script in the script console.
Change Dashboard, Filter or Board Ownership	💡	You can achieve the same result by writing your own script in the script console.
Clean Workflows	💡	You can achieve the same result by writing your own script in the script console.
Clear Groovy Class Loader	N/A	This is not applicable in the Jira Isolated Cloud environment. This is a server-level operation that clears cached Groovy classes from memory. In Cloud, ScriptRunner runs in a separate process managed by Atlassian's infrastructure, and class loading is handled automatically. Users don't have access to server-level memory management.
Configuration Exporter	✗	This is not possible in Jira Isolated Cloud. A third-party tool such as salto.io can provide this. This Data Center tool exports Jira configuration data directly from the server. Cloud instances are managed by Atlassian, and configuration exports are handled through Atlassian's native Cloud migration tools and backup services, not through third-party apps.
Copy Custom Field Values	💡	The Copy values between custom fields script is available in-app from the Example scripts modal in the script console. You can customize this script to meet your requirements.
Copy Project	💡	You can achieve the same result by writing your own script in the script console.
Generate Events	✗	This is not possible in Jira Isolated Cloud. Cloud's asynchronous execution model doesn't support manually triggering Jira events.
Guardrails - Maximum number of comments per issue.	💡	You can use the numberOfComments JQL Keyword to search for issues that exceed a maximum number of comments using a JQL query similar to the one below. `numberOfComments > 5` You can then manually review these issues and delete the comments if needed. You could also automate this by writing your own script in the script console.
Guardrails - Maximum number of unarchived projects	💡	You can achieve the same result by writing your own script in the script console.
Guardrails - Maximum Number of Issue Links Per Issue	💡	You can use the numberOfLinks JQL Keyword to search for issues that exceed a maximum number of links using a JQL query similar to the one below. `numberOfLinks > 5` You can then manually review these issues and delete the links if needed. You could also automate this by writing your own script in the script console.
Guardrails - Maximum Attachment Size	✗	This is not possible in Jira Isolated Cloud. Attachment size limits in Cloud are controlled at the Atlassian infrastructure level, not through individual instance configuration. The REST API doesn't expose endpoints to query or enforce custom attachment size limits.
Guardrails - Maximum Change History Records Per Issue	✗	This is not possible in Jira Isolated Cloud. Change history is managed by Atlassian's Cloud infrastructure. There's no REST API endpoint to query the number of history records per issue or to enforce limits on history retention.
List Scheduled Jobs	💡	You can achieve the same result by writing your own script in the script console.
Re-index Issues	N/A	This is not applicable in the Jira Isolated Cloud environment. Reindexing in Cloud is managed entirely by Atlassian's infrastructure. Unlike Data Center where admins have direct control over indexing, Cloud automatically handles index maintenance. Users cannot and should not manually trigger reindexing operations.
Script Registry	✗	This feature is not currently available in ScriptRunner for Jira Isolated Cloud.
Service Desk Template Comments	✗	This is not possible in Jira Isolated Cloud. This functionality relates to Jira Service Management's internal comment templating system. The Cloud REST API doesn't expose endpoints for managing comment templates in the same way Data Center's Java API does.
Split Custom Field Contexts	💡	You can achieve the same result by writing your own script in the script console.
Switch to a Different User	💡	Log in as another user capability is available natively in Jira.
Test Runner	N/A	This is not applicable in the Jira Isolated Cloud environment. This Data Center tool runs automated tests against ScriptRunner scripts using server-side testing frameworks. Cloud's execution environment doesn't support the same testing infrastructure. Testing must be done through the script console or by running scripts in development environments.
View Server Log Files	N/A	This is not applicable in the Jira Isolated Cloud environment. Cloud users don't have access to server log files - Atlassian manages the infrastructure.

HAPI

Parity summary

In ScriptRunner for Jira Isolated Cloud, HAPI is available but has a limited scope due to the constraints of the Jira Isolated Cloud platform and REST-based architecture. This means that not all the methods available in DC are available in Cloud, as outlined in the table below:

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Application links	N/A	This is not applicable in Jira Isolated Cloud. Application Links is a Data Center feature for connecting different Atlassian applications (Jira to Confluence, Bitbucket, and so on). In Jira Isolated Cloud this concept does not exist in the same way; Cloud products link automatically when they are in the same Atlassian organization. There is no configurable Application Links feature to script against, so HAPI support is not relevant.
Assets	Via fetch	There is no HAPI method for Assets yet. You can still work with Assets from a script using `fetch`: get your workspace ID from the Jira Service Management REST API (`/rest/servicedeskapi/assets/workspace`), then call the Assets REST API for the objects. The Assets API is hosted separately from Jira (on `api.atlassian.com`), so its domain must be allowed for the app's egress before a script can reach it.
Attachments	◐	Isolated Cloud includes: ✓ Add attachments ✓ Get attachments ✓ Read attachments Not included: ✗ Delete attachments ✗ Download URL See our Work with Attachments page for more details.
Comments	◐	Isolated Cloud includes: ✓ Add comments Not included: ✗ Update comments ✗ Retrieve comments ✗ Set comment restrictions ✗ Delete comments See our Work with Comments page for more details.
Entity properties	Via fetch	There is no HAPI method for entity properties yet, but you can read and write them using `fetch` to call the Jira REST API directly, for example the issue properties endpoints at `/rest/api/3/issue/{issueIdOrKey}/properties`. Project, comment, and user properties have equivalent endpoints.
Fields	✓	Isolated Cloud includes: Create fields Read fields Update fields See our Update Work Items page for more details.
Filters	Via fetch	There is no HAPI method for groups yet, but you can manage them using `fetch` to call the Jira REST API directly, for example `/rest/api/3/group` to create or delete a group and `/rest/api/3/group/user` to add or remove members. Group administration requires the script to run with sufficient permissions.
Groups	Via fetch	This is not currently available in ScriptRunner for Jira Isolated Cloud.
Issues	✓	Cloud includes: Create, read, update, and delete work items. Transition work items Search for work items Link issues See the following pages for more details: Create Work Items Update Work Items (Including Fields) Transition Work Items Search for Work Items Work with Links
Permission schemes	Via fetch	There is no HAPI method for permission schemes yet, but you can manage them using `fetch` to call the Jira REST API directly (`/rest/api/3/permissionscheme`). This requires Jira administrator permissions.
Projects	◐	Cloud includes: ✓ Get a space ✓ Create a space Not included: ✗ Archive a space ✗ Delete a space ✗ Update space type See our Work with Spaces page for more details.
Send emails	Via fetch	There is no HAPI method for sending emails yet. You can send an issue notification using `fetch` to call `/rest/api/3/issue/{issueIdOrKey}/notify`, which emails the work item's reporter, assignee, watchers, or chosen users, groups, and roles. It cannot send to arbitrary or external email addresses.
Users	Via fetch	There is no HAPI method for users yet, but you can manage them using `fetch` to call the Jira REST API directly, for example `/rest/api/3/user` to get, create, or delete a user and `/rest/api/3/users/search` to search. User administration requires the script to run with sufficient permissions.
Watchers	Via fetch	Working with watchers is not supported by HAPI. You can manage watchers on existing work items using `fetch` to call the Jira REST API directly (`/rest/api/3/issue/{issueIdOrKey}/watchers`). See our Work with Watchers page for more details.

Integrations

If you need to call external systems to import data into Jira, consider using ScriptRunner Connect, our powerful integration platform that offers this capability and much more.


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Automation for Jira: Asset Object Created Trigger	✗	This is not currently available in ScriptRunner for Jira Isolated Cloud.
Automation for Jira: Asset Object Updated Trigger	✗	This is not currently available in ScriptRunner for Jira Isolated Cloud.
Automation for Jira: Create Asset Action	✗	This is not currently available in ScriptRunner for Jira Isolated Cloud.
Automation for Jira: Execute a ScriptRunner Script Action	✓	The automation actions feature is available in ScriptRunner for Jira Isolated Cloud. With this feature you can create custom actions that you can run inside Jira automation rules.
Automation for Jira: Lookup Asset (Insight) Object Action	✗	This is not currently available in ScriptRunner for Jira Isolated Cloud.
Automation for Jira: Lookup Asset (Insight) Objects from AQL (IQL) Action	✗	This is not currently available in ScriptRunner for Jira Isolated Cloud.
Automation for Jira: Update Asset Action	✗	This is not currently available in ScriptRunner for Jira Isolated Cloud.
Vendors API	✗	This is not currently available in ScriptRunner for Jira Isolated Cloud.

Jobs

Parity summary

This feature is known as Scheduled Jobs in ScriptRunner for Jira Isolated Cloud Isolated Cloud. While this feature has certain limitations in the Isolated Cloud environment, you can still implement various common use cases.

See our Scheduled Job Examples page for a complete collection of pre-written scripts that can be used with Scheduled Jobs.

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Custom Scheduled Job	✓	The scheduled jobs feature is available in ScriptRunner for Jira Isolated Cloud.
Escalation Service	💡	The following examples are available in-app from the Example scripts modal when creating a scheduled job: Escalate open work items Escalate high-priority work items You can customize these scripts to meet your requirements. See our scheduled job examples page for more examples.
Issue Archiving Job	💡	The following examples are available in-app from the Example scripts modal when creating a scheduled job: Archive or unarchive work items Archive completed work items You can customize these scripts to meet your requirements. See our scheduled job examples page for more examples.

JQL Functions

This feature will be implemented as a seperate app called Enhanced Search within Isolated Cloud. This functionality is not available yet. For details on how JQL functions might compare across platforms, see the JQL Functions feature parity section in the ScriptRunner for Jira Data Center documentation.

Listeners

Parity summary

This feature is known as Event Listeners in ScriptRunner for Jira Isolated Cloud. While built-in script listeners are available in the Data Center version and not currently in Cloud, there are many script alternatives that can be executed using a script.

See our Event Listener Examples page for a complete collection of pre-written scripts that can be used with event listeners.

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Adds the current user as a watcher	💡	You can achieve the same result with the event listeners feature and a script.
Clone an issue and links	💡	You can achieve the same result with the event listeners feature and a script.
Create a sub-task	💡	The Create subtasks for new work items script is available in-app from the Example scripts modal when creating an event listener. You can customize this script to meet your requirements.
Custom Listener	✓	The event listeners feature is available in ScriptRunner for Jira Isolated Cloud. Please note that this feature is subject to the constraints of the Isolated Cloud environment. There is a limit of 20 seconds for script executions. After running for 20 seconds, the logs will be collected, and the code will be terminated. Currently, a custom event may not be created and used to trigger listener actions. Events supported in Cloud The list below shows the list of events that Jira Isolated Cloud supports to trigger listener actions from: Attachment Created Attachment Deleted Board Configuration-changed Board Created Board Deleted Board Updated Comment Deleted Comment Mentioned Component Created Component Deleted Component Updated Configuration Changed Expression Failed Field Context Configuration Updated Field Context Created Field Context Deleted Field Context Updated Field Created Field Deleted Field Restored Field Trashed Field Updated Filter Created Filter Deleted Filter Updated Issue Assigned Issue Commented Issue Created Issue Deleted Issue Link Created Issue Link Deleted Issue Mentioned Issue Property Deleted Issue Property Set Issue Type Created Issue Type Deleted Issue Type Updated Issue Updated Issue Viewed Project Archived Project Created Project Deleted Project Restored Project Softdeleted Project Unarchived Project Updated Sprint Closed Sprint Created Sprint Deleted Sprint Started Sprint Updated Timetracking Provider Changed User Created User Deleted User Updated Version Archived Version Created Version Deleted Version Merged Version Moved Version Released Version Unarchived Version Unreleased Version Updated Worklog Created Worklog Deleted Worklog Updated
Execution failure notifier	✗	In Jira Isolated Cloud, the notifications group setting allows you to specify a group of users who will get an email each time a script fails, but this can't be configured to send to other messaging services such as Slack because the notify API doesn't allow you to email external emails.
Fast-track transition an issue	💡	The Transition work items when certain users are assigned script is available in-app from the Example scripts modal when creating an event listener. You can customize this script to meet your requirements.
Fires an event when a condition is true	✗	In Data Center this listener enables you to trigger a specific Jira event based on a custom condition. Once fired, the event can be picked up by a notification scheme, determining who gets alerted. It is not possible to fire a custom event in Isolated Cloud therefore this built-in script cannot be directly replicated in ScriptRunner for Jira Isolated Cloud.
Post a message to slack	💡	The Post new work items to Slack script is available in-app from the Example scripts modal when creating an event listener. You can customize this script to meet your requirements.
Send a custom email (non-issue events)	💡	You can achieve a similar result with the event listeners feature and a script. The notify API doesn't allow you to email external emails and only allows you to notify users, groups, or user fields (such as assignee or reporter) on an issue.
Send a custom email	💡	You can achieve a similar result with the event listeners feature and a script. The notify API doesn't allow you to email external emails and only allows you to notify users, groups, or user fields (such as assignee or reporter) on an issue.
Version Synchronizer	💡	You can achieve a similar result with the event listeners feature and a script.

Mail Handler

The Mail Handler Data Center feature is not currently available in ScriptRunner for Jira Isolated Cloud.


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Mail Handler	✗

Resources

Parity summary

The Resources feature is not available in ScriptRunner for Jira Isolated Cloud.

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Database Connection	✗	This is not possible in Jira Isolated Cloud.
LDAP Connection	✗	This is not possible in Jira Isolated Cloud.
Local Database Connection	✗	This is not possible in Jira Isolated Cloud. "Local" databases are on-premises behind your firewall. Cloud runs in Atlassian's AWS infrastructure and cannot access your internal network due to security isolation.
Slack Connection	✗	This is not possible in Jira Isolated Cloud.

REST Endpoints

This feature is known as HTTP Endpoints in ScriptRunner for Jira Isolated Cloud with known limitations (listed in the table below).


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Rest Endpoints	💡	This feature is known as HTTP endpoints in ScriptRunner for Jira Isolated Cloud. Limitations: Endpoints can't be anonymous. Every request must carry an OAuth 2.0 bearer token with the app's scopes so you can't expose a public, unauthenticated URL (e.g. for a third-party webhook that can't send a Forge token). No control over the response beyond status code and a string body. You can't set response headers, content type, cookies, or redirects, and can't stream or return binary/file content. Structured data must be returned as a stringified body. 20-second execution limit. The request is synchronous and the handler is stopped after 20 seconds, so long-running processing or waiting on slow downstream calls isn't possible. Fixed, environment-specific URL. All endpoints live under `/api/`, with the app and environment IDs baked into the URL; there are no custom paths or domains.

Script Console

The Script Console feature is available in both Data Center and Cloud versions of ScriptRunner. However, there are some Scripting Limitations applied to scripts on Isolated Cloud you should be familiar with.

See our Script Console Examples for a complete collection of pre-written scripts that can be run from the Script Console in ScriptRunner for Jira Isolated Cloud.


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Script Console	✓	Execution limitation: There is a limit of 20 seconds for script executions. After running for 20 seconds, the logs will be collected, and the code will be terminated.

Script Editor

The Script Editor feature is not available in ScriptRunner for Jira Isolated Cloud.


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Script Editor	✗

UI Fragments

Parity summary

The UI Fragments feature is not available in ScriptRunner for Jira Isolated Cloud.

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Custom web item	✗	This is not possible in Jira Isolated Cloud.
Show a web panel	✗	This is not possible in Jira Isolated Cloud.
Create a custom web section	✗	This is not possible in Jira Isolated Cloud.
Hide system or plugin UI element	✗	This is not possible in Jira Isolated Cloud.
Constrained create issue dialog	✗	This is not possible in Jira Isolated Cloud.
Planning board context menu item	✗	This is not possible in Jira Isolated Cloud.
Install web resource	✗	This is not possible in Jira Isolated Cloud.
Custom web item provider	✗	This is not possible in Jira Isolated Cloud.
Raw XML module	✗	This is not possible in Jira Isolated Cloud.

Script Fields

Parity summary

This feature is known as Scripted Fields in ScriptRunner for Jira Isolated Cloud. While built-in scripted fields are available in the Data Center version and not currently in Cloud, there are many alternatives that can be created using a script.

See our Scripted Field Examples page for a complete collection of pre-written scripts that can be used with scripted fields.

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Custom Script Fields	✓	The scripted fields feature is available in ScriptRunner for Jira Isolated Cloud. Additional details: The value of Scripted Fields refreshes on issue view and when an issue containing a Scripted Field is updated. Although full parity is available, it is not possible to perform a full re-index in Jira Isolated Cloud.
Custom Picker	✗	This is not possible in Jira Isolated Cloud.
Database Picker	✗	This is not possible in Jira Isolated Cloud.
Date of the first transition	💡	The Get first transition date script is available in-app from the Example scripts modal when creating a scripted field. You can customize this script to meet your requirements.
Issue(s) Picker	✓	Work item picker fields are available in ScriptRunner for Jira Isolated Cloud.
LDAP Picker Field	✗	This is not possible in Jira Isolated Cloud. Jira Isolated Cloud's REST API doesn't support creating picker field types through apps.
No. of times in a status	💡	The Show days in current status script is available in-app from the Example scripts modal when creating a scripted field. You can customize this script to meet your requirements.
Remote issue(s) picker	✗	This is not possible in Jira Isolated Cloud. Jira Isolated Cloud's REST API doesn't support creating picker field types through apps.
Show parent issue in a hierarchy	💡	The Show parent hierarchy path script is available in-app from the Example scripts modal when creating a scripted field. You can customize this script to meet your requirements.
Time of Last status Change	💡	The Get most recent transition date script is available in-app from the Example scripts modal when creating a scripted field. You can customize this script to meet your requirements.

Settings

There are no settings options in ScriptRunner for Jira Isolated Cloud.


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Script Edit Permissions	✗
Hapi Code Helper	✗
In-App Communications	💡	There is no opt-in for this, but we use in-app banners and popups to communicate information relating to ScriptRunner for Jira Isolated Cloud.
Switch User Function	✗	This is not possible in Jira Isolated Cloud. Atlassian does not provide the API so this cannot be built in Jira Isolated Cloud. However, Jira Isolated Cloud organization admins can switch to different users by using the built in feature as documented by Atlassian.
Anonymous Analytics	✗
User Editor Settings	✗

Workflow Conditions

Parity summary

ScriptRunner workflow functions are available in ScriptRunner for Jira Isolated Cloud as Workflow Rules. In Isolated Cloud, ScriptRunner workflow conditions are called Workflow Restrictions, and they use Jira expressions instead of Groovy.

While built‑in script conditions aren’t directly available in ScriptRunner for Jira Isolated Cloud, you can reproduce their behaviour by creating ScriptRunner Workflow Restriction rules with Jira expressions. See our Workflow Restriction Examples page for a complete collection of Jira expressions that can be used with our workflow restriction feature.

Note: Workflow rules are available in company-managed spaces only on Jira Isolated Cloud. Team-managed spaces are not currently supported.

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
All sub-tasks must be resolved	💡	You can achieve a similar result with the ScriptRunner workflow restriction rule and the subtasks must be done Jira expression example.
Checks the issue has been in a status previously	💡	You can achieve a similar result with the ScriptRunner workflow restriction rule and the work item has been in a specific status previously Jira expression example.
Custom script condition	💡	The ScriptRunner workflow restrictions rule is available in ScriptRunner for Jira Isolated Cloud, however this feature relies on Jira expressions. It does not use Groovy and it is not possible to use the REST API.
Field(s) required condition	💡	You can achieve a similar result with the ScriptRunner workflow restriction rule and the field is required Jira expression example.
Group(s) condition	💡	You can achieve a similar result with the ScriptRunner workflow restriction rule and the restrict to a user group Jira expression example.
JQL query matches condition	✗	This is not possible in Jira Isolated Cloud. Cloud workflow restrictions are restricted to the Jira Expression Framework only, which cannot execute arbitrary JQL queries like Data Center's Groovy-based conditions could. You can achieve a similar result with the ScriptRunner workflow restriction rule, but you must work within the expression language's constraints rather than executing full JQL queries.
Linked issues condition	💡	You can achieve a similar result with the ScriptRunner workflow restriction rule and a linked work item Jira expression example.
Project role(s) condition	💡	You can achieve a similar result with the ScriptRunner workflow restriction rule and the restrict to a space role Jira expression example.
Regular expression condition	💡	You can achieve a similar result with the ScriptRunner workflow restriction rule and the regular expression match Jira expression example.
Simple scripted condition	💡	The ScriptRunner workflow restrictions rule is available in ScriptRunner for Jira Isolated Cloud, however this feature relies on Jira expressions. It does not use Groovy and it is not possible to use the REST API.
User in field(s) condition	💡	You can achieve a similar result with the ScriptRunner workflow restriction rule and a user and permissions Jira expression example.
User(s) condition	💡	You can achieve a similar result with the ScriptRunner workflow restriction rule and a user and permissions Jira expression example.

Workflow Post Functions

Parity summary

ScriptRunner workflow functions are available in ScriptRunner for Jira Isolated Cloud as Workflow Rules. In Isolated Cloud, ScriptRunner post functions are called Workflow Actions.

While built‑in post functions aren't directly available in ScriptRunner for Jira Isolated Cloud, you can reproduce their behaviour by creating ScriptRunner Workflow Action rules with scripts. See our Workflow Action Examples page for a complete collection of exampples that can be used with our workflow action feature.

Note: Workflow rules are available in company-managed spaces only on Jira Isolated Cloud. Team-managed spaces are not currently supported.

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Add a comment to this issue	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script.
Add/remove from sprint	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script.
Adds a comment to linked issues when this issue is transitioned	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script.
Adds the current user as a watcher	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script.
Archive this issue	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script.
Assign to first member of role	💡	The Assign to role members script is available in-app from the Example scripts modal when creating a workflow action. You can customize this script to meet your requirements.
Assign to last role member	💡	The Assign to role members script is available in-app from the Example scripts modal when creating a workflow action. You can customize this script to meet your requirements.
Clear field(s)	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script.
Clones an issue, and links	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script.
Copy field values	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script. In Cloud there is also a Copy Value From Other Field post function built in.
Create a sub-task	💡	The Create a subtask when a work item is transitioned script is available in-app from the Example scripts modal when creating a workflow action. You can customize this script to meet your requirements.
Custom script post-function	✓	The workflow action rule is available in ScriptRunner for Jira Isolated Cloud.
Fast-track transition an issue	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script.
Fires an event when condition is true	✗	In Data Center this post function enables you to trigger a specific Jira event based on a custom condition. Once fired, the event can be picked up by a notification scheme, determining who gets alerted. It is not possible to fire a custom event in Cloud therefore this built-in script cannot be directly replicated in ScriptRunner for Jira Isolated Cloud.
Post a message to Slack	💡	The Send a Slack notification script is available in-app from the Example scripts modal when creating a workflow action. You can customize this script to meet your requirements.
Send a custom email	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script.
Set issue security level depending on the provided condition	💡	You can achieve a similar result with the ScriptRunner workflow action rule and a script.
Transition parent when all subtasks are resolved	💡	The Transition the parent when all subtasks are resolved script is available in-app from the Example scripts modal when creating a workflow action. You can customize this script to meet your requirements.

Workflow Validators

Parity summary

ScriptRunner workflow functions are available in ScriptRunner for Jira Isolated Cloud as Workflow Rules. For validation, you can use ScriptRunner Workflow Validator rules, which support both scripts and Jira expressions.

Built‑in validators are not available in Isolated Cloud, but you can recreate their behaviour by configuring your own validator rules with scripts or Jira expressions. See our Workflow Validator Expression Examples and Workflow Validator Scripted Examples pages for complete collections of examples that can be used with our workflow validator feature.

Note: Workflow rules are available in company-managed spaces only on Jira Isolated Cloud. Team-managed spaces are not currently supported.

Parity details


Server/DC Feature	Cloud Parity	Parity Notes/Alternatives
Custom script validator	✓	You can use ScriptRunner workflow validator rules, which support both scripts and Jira expressions.
Field(s) changed validator	💡	You can achieve a similar result with the ScriptRunner workflow validator rule and a script or Jira expression. If you're creating a scripted workflow validator you can use the Require specific fields to change on transition script available in-app from the Example scripts modal. If you're creating an expression-based workflow validator you can use the field changed Jira expression example.
Field(s) required validator	💡	You can achieve a similar result with the ScriptRunner workflow validator rule and a script or Jira expression. If you're creating a scripted workflow validator you can use the Require specific fields before transition script available in-app from the Example scripts modal. If you're creating an expression-based workflow validator you can use the field required Jira expression example.
Regular expression validator	💡	You can achieve a similar result with the ScriptRunner workflow validator rule and a script or Jira expression. If you're creating an expression-based workflow validator you can use the regular expression match Jira expression example.
Require a comment on transition	💡	You can achieve a similar result with the ScriptRunner workflow validator rule and a script or Jira expression. If you're creating a scripted workflow validator you can use the Require a comment on transition script available in-app from the Example scripts modal. If you're creating an expression-based workflow validator you can use the require a comment Jira expression example.
Simple scripted validator	✓	You can use ScriptRunner workflow validator rules, which support both scripts and Jira expressions.
User in field(s) validator	💡	You can achieve a similar result with the ScriptRunner workflow validator rule and a script or Jira expression. If you're creating a scripted workflow validator you can use the Restrict transition to certain role members script available in-app from the Example scripts modal. If you're creating an expression-based workflow validator you can use a user and permissions Jira expression example.