In this post, we will be discussing ScriptRunner for Jira, an automation and customization app to enhance Jira functionality, developed by Adaptavist.
To learn more about the series, take a look at our introductory post: Jira App Migration: Top 10 Apps Evaluated.
To learn more about the differences in ScriptRunner for Jira Server verses Jira Cloud, refer to our blog post – The ScriptRunner Rundown.
Even though there is some support and documentation available to help you with your migration, it is quite difficult to shift ScriptRunner data to the Cloud. ScriptRunner’s migration journey involves a lot of manual steps and has significant feature parity between environments.
| Feature Compatibility |  |
| Migration Complexity |  |
| Migration Method |  |
| Migration Support Available |  |
| Supported Jira Migration Methods |  |
Feature Compatibility
There are a lot of discrepancies between the features available in ScriptRunner’s Server and Cloud offerings. These differences are largely due to the fact that the fundamental architecture and execution strategy vary greatly between the two environments.
One of the most notable differences in Jira Cloud is it only offers a REST API and not a Java API like Jira Server; therefore, there are differences in the extension points that are available to use in the Atlassian Connect framework. Additionally, for implementations the plugins for the V2 framework are applied behind the firewall.
For a complete list of feature differences, refer to the Feature Parity table provided by ScriptRunner.
Even though there is a significant difference in Server and Cloud features, be sure to check which features you would like migrated, as you may lose little to no functionality if the features that are not supported in Cloud are not presently used by your Server.
Migration Method and Complexity
Migrating ScriptRunner to the Cloud is a tedious process as you must first analyze if each script can be implemented with the native features in Cloud, then write pseudo code for the server script, and finally convert the code to a cloud script. After all of this, you can complete a full site import and add the scripts to your cloud site.
There is no support to migrate with the Jira Cloud Migration Assistant (JCMA) yet, though they are actively working with Atlassian. You can check the status by viewing the public facing Atlassian Jira ticket.
Migration Support Available
Even though ScriptRunner’s migration journey is not straight-forward, there is a migration guide provided by Adaptavist to help you transition to the Cloud. For help with specific issues in your migration, you can always contact Adaptavist by submitting a support request.
Possible Challenges
The most challenging part about migrating ScriptRunner is analyzing each script that has been implemented in the Server and establishing a migration plan. While some of these script goals can be handled with Cloud features, others may need to converted to ScriptRunner Cloud Script.
Despite ScriptRunner for Jira Cloud only supporting a little over half of the features in Jira Server, Adaptavist continues to develop Cloud products and support more features in the Cloud environment.
Resources: