10 easy Jira Cloud automation wins with ScriptRunner
Need to get below your Cloud automation limits fast? Want to use ScriptRunner for your “simple” use cases as well as your complex ones? Here are 10 example scripts for quick wins in Jira Cloud!
ScriptRunner for Jira Cloud's advanced automation feature set and its unlimited automations, regardless of your tier size, makes it a must for many Jira admins when trying to achieve the otherwise impossible in Jira Software, Jira Work Management or Jira Service Management.
But why not put its superpowers to use for all of those not-so-tricky-and-super-common uses too?
If the answer to this question is "I'm not so great at writing scripts": it's time to get your copy-paste on.
Here are 10 example scripts for easy clean-up, issue management and other everyday wins to help you make the most of unlimited automations in Jira Cloud.
"Wait, Andrei, before you jump in: how do I set these scripts up?"
Many of these scripts can be used in different ways in ScriptRunner for Jira Cloud, depending on your need. If you're not super-familiar with the tool, here are your options:
- Run your script in reaction to other events in Jira. We call these Listeners. Bet you can't guess why.
- Run your script on a regular schedule. You can set this up either through Scheduled Jobs, or through the Escalation Service.
- Run your script manually, as-and-when you need it. You do this through the Script Console.
You know what makes most sense for your business, which is why we put the power in your hands!
Perform scheduled bulk updates on Issues returned by a JQL search
Turn routine clean-up tasks into hands-free automations! Schedule bulk updates on issues returned by a JQL search with a simple setup that runs at specific intervals. Imagine flagging all blocked issues inactive for the past 14 days with a simple automation that runs at specific intervals. Remove constant manual intervention and let ScriptRunner do the heavy lifting for you with this script.
Create subtasks when the parent Issue is created
Save time and improve your team's consistency with a set of subtasks that are auto-created when you create a new Issue of a particular type. And you don't have to worry about how many subtasks you have due to those lovely unlimited automations. Get this example script here.
Copy a field value from the parent issue to all subtasks
You've successfully automated the creation of subtasks, but now you also need to copy a specific field value, such as the one in the labels field, for instance, from the parent issue into all subtasks. You can use this example script and have ScriptRunner do that automatically for you.
Close all subtasks when the parent Issue is closed
Having loads of subtasks is great for keeping everyone on track and making sure nothing gets missed, but it can lead to a lot of housekeeping. If only there was a way to close all of your subtasks when the parent Issue is set to Done. Oh, wait. Here’s how.
Create a linked Jira issue for bugs raised in Jira Service Management
This one is a real bandwidth-saver when it comes to working with native Cloud automation limits. Help your Product Managers stay on top of any bugs identified by customers and flagged through the support portal by automatically creating corresponding tickets in the team’s backlog. Grab the example script here.
Add a Definition of Done checklist to each issue
Remove any ambiguity from what ‘Done’ means and align your teams around the quality and consistency of a delivery. Automatically display a Definition of Done checklist on all Story and Task issues so that your teams know when an issue is complete. Get the script here, or read this blog on the Definition of Done for a more detailed look!
Add a customer to an organisation automatically when an issue is created through a Jira Service Management portal
This next automation ensures a seamless onboarding process when your customers create issues via the Jira Service Management portal by automatically adding them to the correct organisation. Optimise your company's request management effortlessly with this script.
Add a comment to each issue created through the Jira Service Management customer portal
Enhance customer satisfaction by using the following automation to add insightful comments to every new issue created via the Jira Service Management portal. Use this script to keep customers informed about SLA expectations and provide clarity on automatic closure, ensuring a transparent and proactive support experience.
Assign an issue based on priority level
Set up an automation that will assign a ticket to a specific person if the priority level is set as ‘High’. This kind of conditional logic can be taken in all kinds of directions depending on the needs of your business to make sure that nothing falls through the cracks. Here's the starting point.
Set a default description for each new issue that is created
Maintain consistency in defining requirements for your teams by automatically setting a default description for new issues that are created. With the help of the Behaviours feature, Jira Admins can enforce a standardized structure for issue descriptions, ensuring that every ticket follows a predefined format. Simplify how issues are created, reduce manual effort, and promote a unified approach to capturing essential requirements with this script.
And there you have it: 10 scripts to implement now in ScriptRunner to save yourself from hitting your automation limits in Jira's native automation feature!
"The limit does not exist."
With ScriptRunner, there is no limit to the amount of automations you can run. It doesn’t matter how big your organisation or its Jira instance is, or how simple or complex your Jira automation needs are.