Supported Features and Limitations

Supported features

This tool is a work in progress and does not yet work for all features. Review the following table for more information:


Feature	Support	Is support for this feature planned?	Notes/Details
Behaviours	Yes	-	Only exports from the Script Registry in ScriptRunner for Jira are supported.The analysis scans the Behaviours configurations from ScriptRunner for Jira Data Center to detect if field types are supported by ScriptRunner for Jira Cloud. Note: Most Behaviours conditions can be used in Cloud when used with a code snippet that the tool provides: `Current user is issue reporter`: Supported with simple snippet `Current user in group`: Supported with simple snippet `Current user is given user`: Supported with additional guidance to convert the DC `user id` to cloud `User in project role`: Supported with simple snippet `Current user is project lead`: Supported with simple snippet `Current user is current assignee`: Supported with simple snippet `Current user is value of user field`: Supported with simple snippet `Workflow Action`: Supported with additional guidance to find `workflow transition ids` `Workflow Step`: Not Supported, but there is a workaround. Since the `status` is not supported in the Transition View, we added guidance to convert this condition to a `Workflow Action` condition instead. `Current user member of group custom field value`: Not supported because `Group Picker` is not available for conditions
Built-in Scripts	-	-	There is nothing to configure in Cloud.Built-in scripts usage data is not exported by the Script Export. Note: "Built-in Script" here refers to the Built-In Script feature of ScriptRunner ( General Configuration → ScriptRunner → Built-in Scripts). Other features, such as Listeners, Workflows, and Jobs, have built-ins that come with ScriptRunner (like the Create a subtask built-in listener) that are supported by this tool and exported by Script Export.
Jobs	Yes	-
JQL Functions	No	?	JQL function usage data is not exported by Script Export. This feature might be supported if JQL function usage is supported by a future version of Script Export.
Listeners	Yes	-
Mail Handler	No	No	This feature is unavailable in ScriptRunner for Jira Cloud, so no configuration is needed.
Resources	No	No	This feature is unavailable in ScriptRunner for Jira Cloud, so no configuration is needed. Some Resources have script alternatives that can be executed in the Script Console in ScriptRunner for Jira Cloud.
REST Endpoints	No	-	This feature is not currently available in ScriptRunner for Jira Cloud. Jira Cloud does not offer custom endpoints. Our recommendation is to use ScriptRunner Connect to fill this gap.
Script Fields	Yes	-	Script Field values are calculated when you view or edit an issue in Cloud, so the values are not automatically migrated from Data Center to Jira Cloud by the Jira Cloud Migration Assistant. After using ScriptRunner Migration Suite to convert your Script Field scripts, paste the code directly into ScriptRunner Cloud or use the ScriptRunner Dev and Deployment Tool to automate deployment. When a Script Field is configured in Cloud, values do not exist because the value is only generated when an issue is viewed or edited. JQL searches against Script Field values may give incomplete or inconsistent results until all issues have had their value calculated. Currently, ScriptRunner Cloud doesn't have a built-in way to sync Script Field values after a migration. Manually viewing or editing affected issues may be sufficient for smaller datasets, while custom scripts can be used for a more automated approach. If you need help, please contact support.
Script Manager	Yes	-	File scripts that are used in a feature, or imported by a feature, will be analysed and stored in the Script Manager in Scriptrunner for Jira Cloud. Scripts that are standalone (e.g. meant to be used run from the Script Console) and not used in a feature, are not analysed.
UI Fragments	Yes	-	Only Web Panels are supported in Cloud, with certain restrictions.
Workflows	Yes	-	Workflow Post Functions are supported for exports from the Script Registry in ScriptRunner for Jira.

Tip: We hope to support more features in the future. Check this page and the changelog for updates.

Limitations

While this tool can do a lot, there are limitations. The assess and analyse tool does not:

Migrate or rewrite scripts (you can use the Dev and Deployment Tool and Migration Agent for this).
Embed the analysis directly into ScriptRunner products.
Generate a migration quote. Human interaction is required to gather inputs and create a proposal for customers.

Cloud parity and limitations

ScriptRunner for Jira Cloud has a different feature set compared to the Data Center version, with some features working differently or having limitations in Cloud. Differences include:

UI Fragments: Only Web Panels are supported, with certain restrictions.
Behaviours: Available but with limitations; many common use cases are still implementable.
Workflow conditions and validators: The Jira Expression Framework is used instead of REST API.

See the Feature Parity and Script Alternatives documentation for more details.

The Assess and Analyse tool accounts for these differences and provides alternatives where they are available.