Compared to the Server version, Jira Cloud no longer requires all automations—even simple ones—to be handled through paid apps like ScriptRunner. However, Jira Automation does have its limitations, and in certain cases, it may still be worth using ScriptRunner or another third-party add-on.
ScriptRunner: Origins and Capabilities
Jira has long supported the ability to develop custom add-ons. Skilled developers could write custom apps to, for example, send tailored notifications within workflows, thereby tailoring Jira to their specific needs. For less experienced developers—or those unfamiliar with the Atlassian ecosystem—this was not as straightforward.
That’s where ScriptRunner came in: an add-on that originally launched as a completely free tool, enabling users to execute Groovy scripts in various parts of Jira.
ScriptRunner quickly gained popularity by dramatically simplifying the scripting process. Over time, it expanded its feature set significantly. In fact, in some of our clients’ instances, we’ve implemented so many ScriptRunner customizations that the environment is barely recognizable as standard Jira.
However, relying heavily on ScriptRunner also comes with drawbacks—most notably, the complexity involved in upgrading Jira to newer versions.
While ScriptRunner is available for Jira Cloud, it differs significantly from the on-premise version. Although it still supports Groovy scripting, it only offers roughly half the functionality due to the inherent limitations of the cloud environment. Writing code is also more demanding, as it now requires interaction with the Jira Cloud REST API instead of directly calling the Java API.
Jira Automation: A Simple Alternative for Building Automations
ScriptRunner’s primary competitor in Jira Cloud is the built-in Jira Automation tool. It covers the vast majority of automation needs and is designed with ease of use in mind. Thanks to its no-code interface, administrators can create powerful automations without any programming knowledge.
Jira Automation is an essential tool for implementing all types of automation. It can respond to a wide array of triggers, including issue creation and updates, field changes, sprint completions, release publications, build status updates in CI/CD pipelines, and even object creation in Insight CMDB.
The tool offers an impressive range of configuration options—supporting conditions, if/else branches, loops, and more.
Naturally, Jira Automation is not as flexible as writing custom code with ScriptRunner. It’s generally sufficient for small to mid-sized organizations, but enterprise-level customers may encounter limitations that lead them to consider ScriptRunner or similar solutions.
In an upcoming blog post, we’ll explore how to build automations, discuss the differences between single- and multi-project automations, and share best practices for managing automation rules effectively.
Script → Automation
With the largest team of certified Atlassian experts in the Czech and Slovak markets, MoroSystems brings deep experience with ScriptRunner. If you’re considering migrating existing scripts to Jira Cloud Automation, contact us at orchestra@morosystems.cz. We’ll help you assess what can be converted, provide guidance for replacements, and recommend alternative solutions where automation isn’t feasible.
Migration to Atlassian Cloud with MoroSystems
Our proven approach starts with a detailed analysis, followed by a clear migration plan, and concludes with thorough testing and production deployment. In short, migrating with an official Atlassian Partner is safe and guarantees success. Visit our Cloud migration page to learn more about how we can support your journey to the cloud.
