When should you choose Jira Automation vs ScriptRunner?

[chickpeafilae]

We use Jira for issue tracking and are looking at automation options. In your experience, what types of tasks are better handled with Jira Automation rules, and when does ScriptRunner make more sense?

[Trudy Claspill]

Hello @chickpeafilae 

Welcome to the Atlassian community.

Does this concern Jira Data Center or Jira Cloud?

If it concerns Jira Cloud, what type of subscription do you have? The number of allowed Automation Rule executions are limited based on your subscription type. The number of rules executing in your system vs. that limitation could influence your decision about using ScriptRunner vs an automation rule.

You should also consider maintenance and scope.

Who is going to have to maintain the solution? Will they have the skills to maintain ScriptRunner code?

When do you need the actions to occur? Are they tied to a workflow transition or some other event?

Do you need to execute against multiple Spaces or only one Space?

How complex is the logic of what you want to do? How many actions do you need to take within the scope of the activity? Complex logic or the need for a lot of actions may be better handled in ScriptRunner than within Automation Rules (where nesting logic structures is not well supported).

[Matt Doar _Adaptavist_]

Great set of questions, Trudy. My take is if it's a reasonably simple task and doesn't happen too often, then go with the vendor's solution, i.e. automation. If it's more complex, then something like ScriptRunner is more powerful and may be the right tool for the job.

Disclaimer: I'm employed by Adaptavist who make ScriptRunner

[housfilae]

Summed up very well.

[Kristian Walker _Adaptavist_]

Hi chickpeafilae,

You may find reading the page we have created here useful to give more of a comparison between Automation and ScriptRunner. 

As Matt said, tho ScriptRunner is generally better used for more complex tasks or where you need to make API calls to third-party systems to retrieve data and then manipulate the data received before doing something with it. 

I hope this helps,

Regards,

Kristian

[Matt Doar _Adaptavist_]

Indeed. I also found a video of Ravi in his car talking about this topic
https://www.youtube.com/watch?v=D83_-qJy-JQ

[Arkadiusz Wroblewski]

Hello @chickpeafilae 

In my experience: start with Jira Automation and only go to ScriptRunner when you hit a wall.

Use Jira Automation when:

it’s the “usual” stuff: copy/set fields, auto-assign, create sub-tasks/linked issues, simple conditions, scheduled cleanup, notifications, routing, basic workflow helpers

you want something easy to maintain by admins and not tied to code

the rule logic stays readable (not 20 branches deep)

Use ScriptRunner when:

you need real logic (complex conditions, transformations, lookups) and Automation becomes a pile of IFs/branches

you hit Cloud limitations like “you can’t target an issue in edit action”, service limits/throttling, or you need more control over how data is written/read

you need custom behavior/validation that Jira doesn’t give you natively (and you want it consistent, not workaround-driven)

you’re building heavier integrations / custom endpoints / more advanced extensions

Rule of thumb:

If it’s clean and simple = Automation.

If you’re fighting the tool or it becomes brittle = ScriptRunner.

[chickpeafilae]

Thank you all for you valueable sugesstions.