Troubleshoot ScriptRunner Migration

You can use this section to learn about some known issues and common issues surrounding migrations to ScriptRunner for Jira Cloud from Server and understand how to use reports if you encounter a failed migration.

Common Issues with ScriptRunner Enhanced Search Server to Cloud Filter Migration

My filter has not migrated to the ScriptRunner Enhanced Search for Jira Cloud app

Filters will not migrate from Server to the ScriptRunner Enhanced Search for Jira Cloud app for the following reasons:

• The filter does not contain any ScriptRunner Enhanced Search for Jira Cloud JQL functions or keywords.

  • These filters will remain as Jira filters, and not be migrated to the ScriptRunner Enhanced Search app.

• The filter contains nested functions such as, issueFunction in linkedIssuesOf(issueFunction in epicsOf(project=TEST))

  • ScriptRunner Enhanced Search for Jira Cloud does not currently support nested Enhanced Search functions, as outlined in our Feature Parity table. However, if you would like to request this feature, you can add your request to our nolt board here.

• The filter contains any Enhanced Search functions or keywords that are not compatible with the Cloud version.

  • Refer to Feature Parity and Script Alternatives for details on which specific functions or keywords are not compatible.

• The filter owner does not exist or does not have the correct permissions. 

  • Ensure that you have migrated your users successfully.

Enhanced Search filters are not syncing or displaying the correct issue results after migration

Filter owners must be given access to the instance

The filter owner user must have access to the Cloud instance to sync Enhanced Search filters. If the user does not have access, the filter will not sync. To ensure that filters are automatically synced and can return the correct results, ensure that all your filter owner users are given access to the ScriptRunner Enhanced Search for Jira Cloud instance. You can find out more information in Atlassian's documentation. 

Filter owners must be given access to any groups and projects they share their filters with

If a filter is shared with a group or project in Jira, but the filter owner cannot access that group in the target instance, the filter may not be synced. Users should be given the required access, or the filters should be updated to reference the correct groups or projects that are accessible to the filter owner.

Filters must have been used in the last two months

Atlassian stores a property against all Jira filters, called approximateLastUsed. This is a timestamp indicating when the filter was last evaluated, meaning the last time the filter was used to execute a search and generate results. If a filter's timestamp exceeds two months, we do not sync that filter. The filter will be synced again only when it is used, and Atlassian updates the approximateLastUsed timestamp to ensure optimal filter syncing performance on your instance.

Why do I see “Your query may take some time” when performing a search?

Cloud infrastructure is very different to Server infrastructure, so it is not possible to compute queries in Cloud in the same way as in Server environments. This means, if you use a search query that requires fetching data from a very high volume of issues, your query may not complete.

If your search takes longer than two minutes to process, it will time out. Complex search queries can take much longer to complete in Cloud than in the Server environment. This two minute searching limit is in place to ensure optimal performance and to cause minimal disruption to your instance.

To prevent your search timing out, it is important to narrow your JQL query scope to ensure that issue results can be processed within two minutes. This can easily be done by narrowing the JQL query scope in your ScriptRunner Enhanced Search function by project, for example:

issueFunction in linkedIssuesOf(“project in (TEST, TEST2) and status in ('In Progress')“)

We have provided some Tips for Writing JQL Queries for your reference. If you are still having trouble crafting your Enhanced Search query, you can contact us via the Adaptavist Product Support Portal. 

Why do I see the “Field 'issueFunction' does not exist or you do not have permission to view it” error message in Jira?

You cannot successfully execute a search with the Enhanced Search JQL functions directly into the Jira issue search page. 

• Jira's built-in search does not support the advanced JQL functions provided by Enhanced Search.
• If you try to copy-paste an Enhanced Search query into the standard Jira search bar, it will not work because the native JQL engine does not recognise those functions.

ScriptRunner Enhanced Search for Jira Cloud JQL functions must be executed in a search from within the Enhanced Search app as they cannot be used directly in the Jira issue search page (also known as the Issue Navigator).

You can still use the Enhanced Search filter within other parts of Jira, for example as a board filter, but it must be created and managed from within the ScriptRunner Enhanced Search for Jira Cloud app itself.

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.

1. Navigate to ScriptRunner → Migration Reports.
2. Click on Migration Reports in the left-hand menu of your ScriptRunner for Jira Cloud instance and the Migration Reports screen appears.
3. 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:

Pitfalls

There are some pitfalls, or known issues, you should be aware of when migrating from ScriptRunner for Jira Server/Data Center to Cloud.

For example, there may be instances where a JQL function on a server needs to be converted to a Cloud JQL keyword.

Asynchronous Event Processing

Asynchronous execution of functions and events means that any updates performed by scripts will happen after the page loads for the user. However, ScriptRunner has a feature that will notify users when issues have been updated. The order of event processing is not preserved, so when multiple scripts are triggered from the same event the ordering is arbitrary and will likely not be consistent.

Event Triggering

Updates made in scripts will cause events to be fired. This means that Script Listeners need to check values before updating them as the script may trigger due to a previous invocation of the same script.

Edit Screen

When using the edit issue API, fields must be visible on the Edit screen for the issue to be modified.

Cloud Logs

Logging in scripts is very helpful when debugging. For Cloud scripts, anything printed to stdout using println or a logger.info('message') call will be available on the Logs page. You'll find these in the Execution History of Script Listeners and Workflow Functions. Using assertions can also help when debugging and diagnosing the behavior of scripts.