Migration Reports
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:
|
| Failed to migrate unsupported in cloud configuration | This message can show in the migration report when a given post function 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 |
Jira's Parent field
If you've renamed or customized the Epic Link default field in your Jira instance, you may notice issues with epic-related queries in ScriptRunner Enhanced Search, such as:
Failures with getting automatic syncing and the most up-to-date results.
Epic-related JQL functions (e.g.,
epicsOf, linkedIssuesOf) not returning expected results.
Atlassian has deprecated the Epic Link field and now recommends using the Parent property to link to epics. Since the Epic Link field was customizable, any epic fields that you have renamed or customized are no longer supported in JQL queries.