Use Reports

ScriptRunner for Jira Cloud provides you with two reports; Migration and Deprecation.

Migration report

If you have yet to complete migrating from ScriptRunner for Jira for Server/DC to Cloud using the Jira Cloud Migration Assistant, when you navigate to ScriptRunner > Migration Reports, you are presented with a landing screen that links to our product documentation.

Once you have completed your migration from ScriptRunner for Jira for Server/DC to Cloud using the Jira Cloud Migration Assistant, you can view a migration report that provides information about any items that failed to migrate and the reason for failure.

Navigate to ScriptRunner > Migration Reports.
Click on Migration Reports in the left-hand menu of your ScriptRunner for Jira Cloud instance and the Migration Reports screen appears.
Click on the Download Report link to download a CSV-format copy of the migration report.

Failed or Incompatible Migrations

When reviewing the downloaded CSV file data, you may see messages informing you of failed or incompatible migration issues. For example:


Message	Definition
Incompatible with cloud, unable to store	It may be the case that a ScriptRunner Server/Data Centre JQL function does not have feature parity in ScriptRunner Cloud so part of that particular query doesn't work in Cloud.
Failed to update filter	Here, an attempt was made to change a migrated filter to make it work in Cloud, but Jira has rejected that filter. There are some specific reasons for this: Jira users that were migrated belong to a group that hasn't been granted product access yet a filter name is duplicated we have a reference to a filter that wasn't actually migrated another Jira error message that would be included in the migration report
Failed to migrate unsupported in cloud configuration	This message can show in the migration report when a given Perform Action is not supported in Cloud. The list of supported functions in Cloud can be found in our documentation. ScriptRunner will automatically remove unsupported Scriptrunner workflow rules from your Cloud instance

Deprecation reports

You can view a report that runs every 24 hours and highlights any Atlassian deprecations in your instance. To view the report:

Navigate to ScriptRunner > Deprecation Reports.
Click Deprecation Reports in the left-hand menu of your ScriptRunner for Jira Cloud instance.
You will see tabbed report types from which you can choose, including: REST Search Endpoints, Epic/Parent Link Fields, Missing Event Properties, and Response Body Links.
The reports highlight ScriptRunner for Jira Cloud features that contain any Atlassian-deprecated endpoints, fields, or event types that have been detected in your instance. Each report highlights the deprecated script Name and UUID. If there are workflow-related scripts, you will also see a Workflow Name link. Similarly, if there are specific Event types in the Missing Event Properties report, you can open the corresponding links to see the details.
When scripts in your instance match deprecated endpoints, fields, or event types, a red numerical indicator appears on the report tab. As shown in the image above, the REST Search Endpoints report has identified one script. Details are provided in the expanded area below, where we can see the related Script Listener.
Note: No scripts found
If no deprecated endpoints, fields, or event types are found, a message will appear in each report informing you of this.
Optional: Click the links provided to go directly to the scripts.
You can now modify these scripts as required. Any items listed in the report will remain there until the related script is updated.
Optional: Click Download CSV to download a copy of the report.