Getting the right version


Automation for Jira is easy to install from the Atlassian Marketplace and you can start creating rules immediately. Once you get going, you'll be guided through the creation of your first automation rules in one of your existing projects, or in a brand new sample project. This blog post on using sample rules shows you how to dive right in using Automation for Jira.

Cloud vs Server

Automation for Jira is available in both Jira Server and Jira Cloud. Functionality is almost identical between the offerings and only differ when one platform doesn't support a particular feature. Cloud and Server both offer a free Version (Lite) and a paid version (Pro).

Marketplace Editions

There are a few different editions of Automation for Jira in the Atlassian marketplace. Below is a summary of the different editions.

Edition Automation for Jira Pro Automation for Jira - Server Lite Automation for Jira - Cloud Lite
Hosting Cloud, Server & Data Center Server Cloud
Subscription Paid Free Free
Includes support Yes Yes Yes
Who it's for? Any team wanting the full power of Automation for Jira. Small teams using just a subset of features. Small teams that don't need to execute many rules per month.
Limitations None - with Pro you get it all. You get unlimited rule executions, but features are restricted. All features, but limited to 300 rule executions per calendar month.

For a full feature by feature comparison, please see the Pro vs Lite table below. You can try out Cloud and Server before buying a licence for up to one month for free.

Data Centre

Data Centre is only available for Automation for Jira Pro


All Marketplace licensing is controlled by Atlassian. You can read more about it here but we have laid out the basics below.

You can trial Automation for Jira Server for up to 6 months. The trial can sometimes be extended by Atlassian upon request.

You can trial Automation for Jira Cloud for a minimum of 30 days. Each account has a billing cycle date, for example the 1st day of each month. If a customer starts an eval on the 15th day of a month, their evaluation will run until the 1st day of the second month in order to give that customer at least 30 days evaluation. In this way, Cloud evaluation licenses can be anywhere from 30 days to 60 days in length.

Pro vs Lite

We offer a free (lite) version of Automation for Jira to enable smaller teams to automate their processes without needing to pay. You can upgrade from Lite to Pro at any time by installing the Pro version. For more details, please read our detailed guides on upgrading. You can downgrade from Pro to Lite by first uninstalling Pro (in Manage add-ons), then re-enabling Lite.


In server, if you downgrade from Pro to Lite, any automation rules using Pro-only rule components will no longer work. It is recommended to check which components you use before downgrading.

Feature checklist

Automation for Jira Pro Automation for Jira - Server Lite Automation for Jira - Cloud Lite
Subscription model Paid Free Free
Jira Data Centre 🚫 N/A
Includes support
No. of rule executions Unlimited Unlimited 300 per calendar month
Global rules
Multi-project rules 🚫
Project admin access 🚫
Working with related issues 🚫
Field value changed 🚫
Incoming webhook 🚫
Issue assigned
Issue commented
Issue created
Issue deleted
Issue event
Issue linked 🚫
Issue moved 🚫
Issue property updated 🚫
Issue transitioned
Issue updated
Manual trigger 🚫
Multiple issue events
Service limit breached
SLA threshold breached 🚫
Sprint events 🚫
Version events 🚫
Work logged 🚫
Compare condition 🚫
If/else block 🚫
Issue attachments condition 🚫
JQL condition
Related issues condition 🚫
User condition
Add Service Desk Customer 🚫
Assign issue
Clone issue 🚫
Comment on issue 🚫
Create issue 🚫
Create Service Desk request
Create sub-tasks 🚫
Create version 🚫
Delete attachments
Delete issue
Edit issue
Link issue 🚫
Log action
Log work 🚫
Manage watchers 🚫
Publish event 🚫
Re-fetch issue data
Release version 🚫
Send email 🚫
Send Microsoft Teams message 🚫
Send Slack message 🚫
Send Twilio notification 🚫
Send webhook 🚫
Set entity property
Transition issue