Migrating ScriptRunner for Jira from Server
Overview
- Alternative hosting options
Your alternative hosting options for ScriptRunner for Jira are Cloud and Data Center. This page takes a look at the differences and which route might suit you best.
- Feature comparison
Everything the Server version of the app can do, the Data Center version can too.
On Cloud, there are some notable differences, highlighted below.
Comparing Cloud functionality at-a-glance
Expand each feature below to see more details. Remember, some things work a little differently on Cloud, so we'd recommend taking a closer look at documentation to understand the differences if these features are critical for your processes.
There is ongoing development work with Atlassian to make this happen as a priority. We expect this to be available in alpha/beta in early 2022.
Implemented as JQL Keywords and Enhanced Search.
Details of differences available here.
Jira Cloud Conditions and Validators are achieved through the use of Jira Expressions.
Jira Cloud Conditions and Validators are achieved through the use of Jira Expressions.
Workflow postfunctions have been fully implemented on ScriptRunner for Jira Cloud.
Partially possible with Script Listeners and Scripted Fields. We continue to work with Atlassian for required access to deliver full feature.
We’re actively seeking further input into use cases: please reach out to us to discuss!
This is on our roadmap, currently in scoping. Please reach out to us to discuss!
We’re keen to hear from you about what you’d like to see on ScriptRunner for Jira Cloud. You can upvote suggestions or submit your requests here.
For more specifics about how these features work in Cloud, please check out the ScriptRunner for Jira Cloud documentation or join our upcoming migration webinar to see a side-by-side demo of the Cloud and on-premise apps.
Migration process: ScriptRunner from Jira Server to Cloud
There are two ways to migrate from ScriptRunner for Jira Server/Data Center to Cloud: manually, or using the Atlassian Cloud Migration Assistant.
Broadly speaking, the process is as follows:
- Analyse the purpose of your scripts
- Identify the equivalent feature in Cloud
- Adjust your scripts to be Cloud-ready (explained below)
Full details and more possible gotchas for each method are outlined in the documentation below.
One of the biggest gotchas for migration is the rewriting of scripts. As mentioned in the ScriptRunner migration FAQs section, any migration from Server to Cloud requires some rewriting of your scripts. For instance, interactions with APIs will need to be replaced with calls to the appropriate REST APIs due to differences between Atlassian Cloud and Server infrastructure.
If the equivalent feature in Cloud for what you need does not exist yet, please let us know. We’re prioritising development based on feedback from you!
Migration process: ScriptRunner from Jira Server to Data Center
When it comes to migrating Jira on-premise, there are two main types of migration:
- Non-clustered: this is as simple as updating your ScriptRunner for Jira license
- Clustered: this also requires you to move your home directory to a shared location that all nodes can access
Full details of steps involved and potential gotchas to look out for can be found via the following link.
Useful tools for migrations
Jira Cloud Migration Assistant
This useful app comes as a pre-installed app on Jira Server and Data Center from version 7.6.0 onwards. Use it as a planning tool before you begin your migration to help you take stock of what apps you have, how they work on Cloud and more.
Jira Cloud Migration Assistant (JCMA) then helps you with the app migration journey itself. Side by side with Atlassian, we’ve been working on integrating ScriptRunner for Jira into JCMA to help you achieve the easiest migration path possible.
Adaptavist Microscope
Get rapid insight into your Server or Data Center Jira instance ahead of migrations. Conduct project and workflow audits to save weeks of exploratory work.
Project Audit can be used to identify your most and least used projects, archived or unused projects, and more.
Workflow Audit generates a list of your workflow functions to unlock quick insight into your most critical and most underutilised apps and functions.
Stay in the loop
The best way to keep up to date on what’s happening with ScriptRunner for Jira Cloud is our ongoing webinar series. View previous sessions below and sign up for the next one!
Previous migration webinars
We ran this webinar back in June 2021. Please view the above on-demand webinar for the most up-to-date information!
Need help writing scripts for Cloud?
Don’t have the bandwidth to rewrite your scripts in-house? Whether it’s time restrictions, personnel changes or a lack of confidence holding you back, our scripting service can help get you up and running quicker.
- Get production-ready scripts on demand
- Available across ScriptRunner for Jira, Confluence, or Bitbucket
- Available across Server, Data Center and Cloud
Our team of Groovy and ScriptRunner experts are here to help you make the most of ScriptRunner and get back to what you do best: on premise or on Cloud!
Migration services
Did you know that we were named Atlassian Partner of the Year 2020 for Cloud Migration Services?
With a tried-and-tested, best practice approach to Atlassian tool migration, we’ve helped some of the world’s leading organisations move to Atlassian Cloud—guiding them every step of the way.
Let our team of migration experts help with scoping and planning through to delivery of your migration project.