What we do
Tools
Industries
Department
How we workLet's talk →
Home/Jira
Jira Automation

Jira Automation, Explained: Triggers, Conditions, Actions and Your Step Allowance

Jira automation is the no-code rule builder that comes with every Jira Cloud plan. A rule waits for something to happen, checks whether it should act, then does the work a person would otherwise click through. Below: how a rule is put together, one built from scratch, what a month of rules costs now that Atlassian counts steps, and the usual reasons a rule stays silent.

Where Jira stops

Tickets stay inside dev's sprints while sales, support and ops live elsewhere.

Stuck on Jira? Let's solve it →
How a rule is put together

Trigger: the event that starts the rule. A work item is created, a field changes, a status transition happens, a schedule comes round, or another system calls the rule's incoming webhook.

Conditions: optional checks that stop the rule unless they pass, such as priority is Highest or the reporter belongs to a group. A JQL condition covers anything more specific.

Actions: what the rule does. Assign, transition, edit a field, comment, create a work item, send an email, post to Slack or Microsoft Teams, or send a web request to another system.

Branches: run the next components against related items instead, such as the parent, every sub-task, or the results of a JQL search.

Where to build one: a space admin can add rules from that space's settings. A Jira admin builds rules across several spaces in global automation.

Settings ⚙ System Global automation

Build a first rule: close the parent once its last sub-task is done

A small rule that saves a click on every story, and shows how triggers, conditions and branches fit together.

  1. 1

    Pick the trigger

    Create a rule and choose the work item transitioned trigger. Set the destination status to Done and leave the starting status blank, so any route into Done counts.

  2. 2

    Narrow it to sub-tasks

    Add a condition on the work item type so the rule only carries on when the item that moved is a sub-task. Without it, every story moving to Done starts the rule too.

  3. 3

    Branch to the parent

    Add a branch for the parent. Everything you place inside the branch now acts on the parent, not on the sub-task that triggered the rule.

  4. 4

    Check the siblings

    Inside the branch, add the related work items condition and require that all sub-tasks are in Done. If even one is still open, the rule stops here.

    Watch for: a run that stops at a condition and does nothing doesn't use any of your step allowance, so this check costs nothing on the runs that end early.

  5. 5

    Transition the parent

    Add the transition action and send the parent to Done.

    Watch for: the parent's workflow must allow a move to Done from whatever status it's in. If it doesn't, the audit log shows the failure.

  6. 6

    Name it, switch it on, read the audit log

    Give the rule a name your team will recognise, check its scope and the user it runs as, and turn it on. Close a test sub-task, then open the rule's audit log to see each component that ran.

What a month of rules costs in automation steps

Atlassian now meters automation in steps rather than rule runs. Every trigger, condition, action and branch that runs is one step, and the monthly allowance is pooled across your organization: 150 on Free, then 400, 750 or 1,000 per user on Standard, Premium and Enterprise.

Example: a 10-user Jira Standard site. Your rules and volumes will differ.
Monthly allowance, 10 users × 400 steps 4,000 steps
The sub-task rule above, about 5 steps each time it closes a parent (About 120 parents closed) − 600
Bug triage: trigger, condition, assign, Slack message (4 steps on each of 300 new bugs) − 1,200
Daily sweep that comments on about 30 stale items (32 steps a run, every day) − 960
Web request to the sales system when a deal ticket closes (3 steps on each of 400 tickets) − 1,200
Left at month end 40 steps

Go past the allowance with extra usage switched on and Atlassian charges $0.50 per 1,000 extra steps. With it switched off, your flows stop until the allowance resets. Log actions, variables and lookups don't count. Your real numbers are under Settings, System, Global automation, Usage.

Why a Jira automation rule didn't fire, or did the wrong thing

Open the rule's audit log first. Most of these show up there once you know what to look for.

It ignores changes made by another rule

How you'll know: The rule works when a person edits the item, but not when a different rule makes the same change.

Fix: Rules don't react to other rules' actions unless you allow it in the rule details. Switch it on with care, because two rules that trigger each other make a loop.

The rule runs as someone without permission

How you'll know: The audit log shows a permission error on an action.

Fix: Every rule runs as its actor, the automation user by default. Give that actor permission in the space, or change the actor to an account that has it.

It works in one space and nowhere else

How you'll know: Same kind of work item, no reaction in the second space.

Fix: The rule's scope is a single space. A Jira admin can widen it to several spaces or make it global in the rule details.

A smart value comes out blank

How you'll know: A comment or email shows an empty gap where a field should be.

Fix: Smart values are case-sensitive and custom fields need the right name or ID. Add a log action that prints the value. It doesn't use any steps.

A scheduled rule eats the allowance

How you'll know: Usage jumps and one scheduled rule sits at the top of the Usage tab.

Fix: Tighten its JQL, and tick the option to only include work items that changed since the last run, so it stops reprocessing the same items every day.

Every rule stopped on the same day

How you'll know: Nothing fires, and the audit logs show nothing new.

Fix: The organization's step allowance ran out with extra usage switched off. Raise the limit, switch extra usage on, or trim the heaviest rules.

Where Jira automation reaches on its own, and where it stops

Built in

Inside Atlassian, plus chat and email

  • Anything inside Jira: fields, transitions, assignments, comments and new work items.
  • Emails, and messages to Slack or Microsoft Teams channels.
  • An incoming webhook trigger, so another system can start a rule.
Needs building

Systems that have to act on what happened

  • Send web request pushes one payload. Something on the other end has to receive it, check it and do the work.
  • Atlassian doesn't queue a failed request to try later. If the other system is down, the run fails and you find out from the audit log.
  • Worklogs to invoice lines, resolutions to a CRM record or a customer's helpdesk ticket, each with that system's own fields and rules.

Keep the built-in rules for everything that stays in Jira. n-frames builds the part where a rule's job ends in someone else's software: the invoicing tool, the CRM, or the helpdesk your customers write to.

A SaaS support desk feeding a Jira backlog

A software company's support team working from a helpdesk, with engineering in Jira.

Before

Support reported each bug by pasting the details into Jira by hand.

Engineers came back asking for reproduction steps the customer had already given.

After

A bug flagged in the helpdesk creates the Jira work item with the customer, environment and steps filled in.

Engineers open the item and start on the fix instead of a round of questions.

Questions people ask

Is Jira automation free?

It's included with every Jira Cloud plan, with a monthly allowance of automation steps that grows with your plan and user count. Past that, Atlassian charges for extra steps if extra usage is on, or pauses your rules if it's off.

How does Atlassian count Jira automation usage now?

In steps. Each trigger, condition, action, branch and loop that runs counts as one, and the allowance is shared across your whole organization. A run that ends without doing anything doesn't count, and nor do log actions, variables or work item lookups.

What triggers are available in Jira automation?

The common ones are work item created, field value changed, work item transitioned, comment added, sprint and version events, scheduled triggers that run on a timer, manual triggers a person starts from the item, and an incoming webhook that another system can call.

Can Jira automation send data to another system?

Yes, with the send web request action, which posts a payload to a URL you choose. The receiving side still has to be built: something that checks the request, maps the Jira fields to the other system and copes when that system is down.

What is Jira software?

Jira is Atlassian's work tracker, built mainly for software teams. Work is logged as work items, such as bugs, stories and tasks, that move through a workflow on a board, usually in sprints for Scrum teams or a continuous flow for Kanban.

How much does Jira cost?

Jira is priced per user per month, with a Free plan for small teams and Standard, Premium and Enterprise plans that add more automation allowance, storage and admin controls. Atlassian's pricing page has the current numbers.

What is a Jira software license, and do I have to manage it myself?

On Jira Cloud the license is your plan and user count, and Atlassian runs the hosting. Self-managed Jira Data Center is a separate, heavier license for organizations running their own servers.

Does Jira have built-in time tracking?

Yes. You can log time on a work item and estimate what's left. It won't turn those hours into an invoice or check them against a client's budget, which is the connection n-frames builds between Jira worklogs and your invoicing tool.

What are the main alternatives to Jira?

Linear, Asana and ClickUp come up most, usually from teams wanting something lighter. Switching rarely fixes a gap between Jira and the rest of the business, though, because the new tracker has the same edge.

Who can build Jira automation that reaches outside Atlassian?

n-frames builds the receiver for a rule's web request, the mapping into your other system, and the retries and alerts for when that system doesn't answer. Without that, the job falls to whoever on your team can write and host a small web service.

Keep reading

Jira Automation Rules Copy-ready Jira automation rules with the trigger, condition, action and smart values for each, the hard limits per plan, and what each audit log status says.How to Change a Jira Workflow Safely How to change a Jira workflow in team-managed and company-managed spaces: statuses, transitions, rules, schemes, and what an edit does to open work.JQL Cheat Sheet A JQL cheat sheet: copy-ready Jira queries for status, people, dates, sprints and history, every operator, the mistakes that hide results, and saving filters.Jira Webhook Setup How to create a Jira webhook, what the payload and headers contain, how Jira retries and signs deliveries, and when an automation web request fits better.Jira API How to call the Jira Cloud REST API, make a token, create and move an issue, and fix the changes that break older Jira API scripts.Jira Integrations Which Jira integrations already exist for Slack, Teams and GitHub, when an Automation rule is enough, and what gets built when no Marketplace app fits.Jira Service Desk Setup, Under Its New Name Jira Service Desk is now Jira Service Management. Who needs a license, how to set up request types, SLAs and queues in order, and what agents still can't see.Jira and Confluence How to show Jira work on a Confluence page, turn page text into tickets, and which tool does what, plus where the Jira Confluence link stops reaching.Jira Reporting Which Jira report or dashboard gadget answers which question, the numbers none show (time in status, cross-board velocity, history), and how to get them.Jira Issue Template Jira Cloud has no saved issue template on the Create screen in most setups. Five ways to get one: block templates, defaults, clones, automation or an app.Jira Smartsheet Connector How Smartsheet's Jira Connector works, who can buy it, setup choices you can't undo, what it won't sync, and how Jira data reaches Power BI and SharePoint.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.