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