Jira Automation (Atlassian)

This Jira Automation review covers what the feature is used for, how an automation rule works, Jira Automation pricing and the new usage limits, where it shines and falls short, and how it compares with other automation tools. Jira Automation is built into Jira Cloud, Jira Service Management and Confluence, and it is also available in Jira Software Data Center. You build each automation rule in a visual editor: a trigger starts it, conditions decide whether it continues, and actions perform tasks such as assigning an issue, changing a status or sending notifications. Atlassian now calls rules "flows" in parts of its documentation; the idea is the same.

What is Jira Automation used for?

Teams use Jira Automation to automate tasks and take repetitive work off people's plates. For example, a company can assign new bugs to the team member with the lowest workload, complete a parent issue when every sub-task is done, copy fields from an epic to its stories, remind an assignee when a work item has sat in a status too long, and post a message in Slack or Microsoft Teams when a high-priority issue is created. Other common rules add a comment with a summary when work items are created from email, assign work items to a specific user by component, and turn on a label when a due date passes. Service teams automate triage, SLAs and customer notifications in Jira Service Management. Engineering teams connect Jira to GitHub or Bitbucket so that commits, pull requests and deployments move work items through the workflow.

Because every automation rule lives in the project settings or the global automation screen, admins can see and manage the processes that run across the Jira instance in one place. Rules can be scoped to a single project, several projects or the whole site, which lets each team focus on its own processes while admins keep the relevant rules for the company in one list.

Key features

• Triggers, conditions and actions: the three parts of every automation rule. Triggers include issue created, field changed, status transition, scheduled times and incoming webhooks.
• Branches and smart values: branches run actions on related work items, such as sub-tasks, linked issues or all issues returned by a JQL search. Smart values insert data like the reporter or due date into fields and messages.
• Rule library and templates: start from a template instead of from scratch and refine it.
• Natural language rules: describe a rule in plain English and Atlassian's Rovo AI drafts it for you to review.
• Audit log: every rule has an audit log that shows each run, the work items it changed, the actions it took and any errors, which makes debugging practical.
• Integrations: Slack, Microsoft Teams, GitHub, Bitbucket, GitLab and outgoing webhooks to call other tools.
• Usage monitoring: admins see how much of the monthly allowance each rule consumes.

Jira Automation pricing

Jira Automation has no separate price. It is included in every Jira plan, and the plan sets how much automation you can run. According to Atlassian's usage documentation (September 2026), Cloud allowances are counted in automation steps per month:

• Free: 150 steps per month for the subscription (Jira Free allows up to 10 users).
• Standard: 400 steps per user per month.
• Premium: 750 steps per user per month.
• Enterprise: 1,000 steps per user per month.

Each trigger, condition, action, branch and loop that executes counts as one step, whether the run succeeds, fails or does nothing. System components, throttled runs and Rovo agent work are not counted. Allowances are pooled at the organization level across Jira, Confluence and other Atlassian apps and refresh monthly. Before this model, Atlassian counted rule executions against a monthly cap per product; you will still see that term in older Atlassian Community answers.

Jira itself costs about $7.91 per user per month on Standard and $14.54 on Premium with annual billing, according to third-party price trackers such as Automation Atlas; Atlassian's own pricing page is the place to confirm the price for your user count.

The cost surprise to check is what happens at the monthly limit. An older Atlassian knowledge-base article says all rules stop until the limit resets on the first of the next month. The newer usage documentation says extra usage will be billed from December 3, 2026 at $0.50 per 1,000 additional steps. Either way, a rule with many conditions and branches that fires on every issue update can use up a team's allowance quickly, so check the usage screen before you roll out rules across all projects. A useful habit is to note which rules run on every issue update and add a condition early, so the rule stops before its actions run when it is not relevant.

Service limits and complex scenarios

Separate from the monthly allowance, Atlassian's service limits protect the platform. A standard rule can have at most 65 components; advanced flows allow up to 500. Each rule may process for 60 minutes per 12 hours, a branch fetches at most 150 related items per run, and a rule that triggers itself stops after 10 loops. When a limit is hit, the audit log shows a THROTTLED status and the rule may be disabled. For complex scenarios, such as heavy scripting or calculations across thousands of issues, teams add apps like ScriptRunner or Power Scripts, which need some code.

Getting started with Jira Automation

Open project settings, choose Automation and create a rule from a template or from scratch; site admins can also add global rules for the whole instance. Pick a trigger, add a condition, then add an action, and use the rule's audit log to confirm it works. Test in a sandbox or a small project first. The Atlassian Community and Atlassian University have many example rules, so most admins who are familiar with Jira workflows learn the basics in an afternoon.

Where Jira Automation shines — and where it falls short

Strengths:

• Included in every Jira plan, with no extra license to buy.
• No-code builder that Jira admins and team leads can use in just a few clicks.
• Deep access to Jira data: fields, statuses, JQL, versions and linked work items.
• Audit log and usage monitoring for every rule.

Trade-offs:

• Monthly step allowances can run out, and the rules around overage are changing.
• Limited outside the Atlassian ecosystem compared with general automation platforms.
• Complex logic hits the 65-component limit or needs scripting apps.
• Smart values and JQL search take time to learn for new admins, and large rule sets may need the bigger step allowance of Premium or Enterprise.

How Jira Automation compares

• Zapier and Make: general automation across thousands of apps, better when Jira is one of many tools.
• n8n: open-source workflow automation you can self-host.
• Microsoft Power Automate: the Microsoft 365 equivalent.
• Slack Workflow Builder: simple automations inside Slack.
• Trello Power-Ups: Atlassian's automation for Trello boards.
• ServiceNow: enterprise IT workflow automation beyond Jira Service Management.

Is Jira Automation worth it?

Yes for any team already on Jira. It is included in the plan, it removes repetitive tasks such as assignments, status updates and notifications, and admins can manage it without code. It is less of a fit when your processes span many non-Atlassian apps, when you need heavy calculations or scripting, or when a large rule set would exceed the monthly allowance on the Standard plan. If you need help designing a rule set or connecting Jira to the rest of your stack, the low-code agencies and developers on LowCodeDevs can take it on.

Sources

• How is my automation usage calculated?, Atlassian Support: steps per plan, pooling and extra usage from December 2026.
• Automation service limits, Atlassian Support: component, time, queue and branch limits.
• Automation limits vs usage, Atlassian Support: older description in which rules stop at the monthly limit.
• What is Jira Automation?, Atlassian: triggers, conditions, actions and Rovo rule creation.
• Get started with Jira automation, Atlassian: Data Center automation.
• Simplifying Jira tasks, Salto: ScriptRunner and Power Scripts (written by a vendor of Jira tooling; its statement that rules always stop until next month predates Atlassian's step-based usage model).
• Jira pricing explained, Automation Atlas: third-party Jira price estimates.