Work in progress ... this is still incomplete. Please nudge us to help us understand, that this needs more attention.
| Criteria | Automation for Jira
| ScriptRunner for Jira
| Jira Automation Plugin
| Automation Tools for Jira
|
|---|---|---|---|---|
| Available for Jira Server? |  |
|
|
|
| Available for Jira Cloud | | |  | |
| License Costs | HIGH FOR UPPER USER TIERS | HIGH FOR UPPER USER TIERS | FREE | CHEAP |
| Vendor maturity | NEW | LARGE VENDOR | IT'S ATLASSIAN | NEW |
| Vendor background info | Ex-Atlassians, Creators of the free plugin | Backed by big vendor Adaptavist | By Atlassian | Unknown to us |
| Plugin evaluation | Very easy to use surface | Market leading solution, very versatile | Largely unmaintained | Largely a copy of free plugin |
| Market share / adoption | LOW | HIGH | HIGH | VERY LOW |
Comparision fact sheet by Codebarrel
Some of their comments from an interview
"The thing with ScriptRunner is that it can cover pretty much anything that's available through Jira's API (but it also lets you do scary things from a security/resource utilisation point of view). We aim to cover the majority of automation use-cases a team is faced with in Jira."
"Switching from one to the other is difficult. We can't really write an 'importer' and admins would have to convert scripts to automation rules manually..."
"Recommending one over the other is difficult. If you have something really detailed and specific to your team's process you're trying to automate, and you have coding knowledge and the time to invest in learning Jira's apis then scriptrunner is probably the solution. Otherwise go with Automation for Jira - it will save you a huge amount of time and headache"
"No ScriptRunner doesn't really have a visual interface. There are some things they seem to have a UI for (like the create sub-tasks for example), but it's a pretty complex UI in general."