Who are these tutorials for?

These tutorials are for Jira administrators who don’t know how to write Groovy code, but want to use ScriptRunner to automate and improve their Jira instance. The goal of these tutorials is to break down the barrier-to-entry for ScriptRunner and help you see what it can do and how easy it is to use.

About our tutorials

To make the most of these tutorials, you don’t need any scripting experience, but you should feel comfortable creating and managing issues, building workflows, and working with Jira administration functions. In these tutorials, you can learn about some of the main functions of ScriptRunner and how to use them.

What we don’t cover

While we do mention areas you can use custom scripts, along with some tips on how to use custom script options, we don’t teach any Groovy in this course. This course focuses more on the business user or administrator who doesn’t have, or necessarily need, scripting knowledge, so we don’t teach you how to write scripts.

While available to ScriptRunner users, this course also doesn’t include working through script fragments or using the REST API. For coverage on topics we can’t cover, we recommend visiting the dedicated Features page in our documentation.

Great Adventure

During these tutorials, you will notice a reference to Great Adventure.

What is Great Adventure?

Great Adventure is the fictitious company we use to help provide use cases and examples of concepts covered. Great Adventure is a company that organizes specialized holidays for the discerning tourist.

Great Adventure has the same problems and issues faced by most companies. Great Adventure needs to automate more of its process using ScriptRunner, especially in their Virtual Tour and Finance teams. For instance, issues are sometimes raised that are not resolved in an appropriate time period. Obviously, management wishes to be able to identify these issues more readily and have them escalated. 

Important things to remember

Use a staging or test environment

You should avoid working in your production environment for testing because ScriptRunner loosens the Jira reins just enough to be dangerous. We recommend that you test ScriptRunner functionality in a staging or test environment until proven to work.

Caution with recursive searches

You must also be careful with recursive searches, as they can stop Jira. To avoid this happening:

  • Provide a subquery in your search to help limit results.

  • Use a limited version of JQL functions, to make sure you don’t go too far and can't find your way back.

Caution with Groovy scripts

We recommend that you are careful when you use groovy scripts found on the Internet. Make sure your script comes from a reputable source, such as the Adaptavist Library.

Make sure you have a look at the rest of our documentation. It contains discussions regarding efficiency, performance, and comparisons between differing approaches. Read it carefully during the planning stage, before you attempt to run something you are not 100% sure of.

Not sure how to navigate to ScriptRunner? Visit the Navigation guide.

Let's get started!

Our tutorials are listed below. You can follow these tutorials in order (as displayed here), as part of a full course, or as stand-alone lessons.

On this page