Jira Automation Pricing Guide: Free Tier Limits and What You Actually Need

Verdict up front: Most teams overshoot or undershoot Jira Automation tier. Free tier (100 exec/month) covers personal use only. Standard (5k exec/month) covers teams up to ~100 users. Premium (unlimited + cross-project) is mandatory once you have multi-project workflows. The hidden cost is hitting limits mid-month and watching your bot stop firing.

The Jira Automation tiers

• Jira Free: 100 single-project rule executions/month, no cross-project rules
• Jira Standard: 5,000 rule executions/month, no cross-project rules
• Jira Premium: Unlimited rule executions, full cross-project automation
• Jira Enterprise: Same as Premium + multi-instance, SSO+, advanced governance

Atlassian counts executions globally across your Jira site, not per project. A 500-issue bulk update from one rule = 500 executions. This is the source of most "we hit the limit" surprises.

Real cost at different team sizes

Standard pricing (€8.60/user/month) applies to all Jira features including Automation Standard limits.

The €4,200/month delta between Standard and Premium at 500 users is real. Don't upgrade everyone if only one team needs cross-project — split Jira sites if it makes sense.

How rule executions add up faster than you think

Common rules and their typical monthly execution cost for a 50-person team:

• "Auto-assign new bugs to team lead": ~100 executions/month (1 per new bug)
• "Sync status to linked tickets": ~500 executions/month (status changes are frequent)
• "Notify Slack channel on transition": ~800 executions/month (heavy usage)
• "Daily SLA breach check (runs at 9am): ~250 executions/month (scheduled, can scan many issues)
• "Auto-close stale tickets after 30 days": ~50 executions/month (low frequency, can be high-multiplier)
• "Create subtasks from epic template": ~200 executions/month (each epic spawns 10 subtasks)

Total: ~1,900 executions/month for 6 reasonable rules. Standard's 5,000 limit gives you headroom for ~15-20 such rules. Past that, Premium.

The hidden execution multipliers

Branch rules and loops compound fast. A rule like "for each linked issue in this epic, update status" counts as N executions where N = number of linked issues. We've seen teams blow through 5,000 executions in a single day because of one badly-scoped bulk rule.

How to keep execution count down:

• Use scheduled rules instead of triggered rules when possible (1 scheduled execution = 1 unit, regardless of how many issues processed)
• Combine multiple actions into one rule (avoid 5 rules each watching the same trigger)
• Filter early — use issue conditions before branching
• Avoid "log audit" rules that fire on every change

When to upgrade from Standard to Premium

• You exceed 5,000 executions/month consistently (check usage in Automation logs)
• You need cross-project automation (e.g. "when issue closed in Project A, create issue in Project B")
• You need Atlassian Intelligence (AI-suggested rules, AI summary actions) — Premium-only
• You need 99.9% uptime SLA
• You need advanced roadmaps

When to NOT upgrade

• You're below 3,000 executions/month — Standard fits
• Only one team needs cross-project — consolidate them into one project or accept Standard's limits
• You can rewrite rules to be more efficient (combining 3 trigger-based rules into 1 scheduled rule)

The external automation option

For teams that need heavy automation but want to stay on Standard, external tools work:

• Zapier: €20/month for 750 tasks. Limited Jira actions but enough for simple integrations.
• Make (formerly Integromat): €9/month for 10k operations. More granular Jira support than Zapier.
• n8n self-hosted: €0/month + DigitalOcean droplet (€6/month). Unlimited operations. Open source.
• Custom scripts on Cloudflare Workers: €5/month for 10M requests. Direct Jira REST API calls.

For a 100-person team that would need Premium (€1,700/month) just for automation, n8n on a droplet for €11/month total often does the job. Trade-off: you need to build the rules in n8n instead of Jira's native editor — less polish, more flexibility.

Premium-only features that might justify the upgrade

• Cross-project rules: the big one
• Atlassian Intelligence: AI rule suggestions, smart summaries
• Sandbox + release tracks: test rules before production
• Advanced roadmaps: portfolio management across projects
• Project archiving: stop paying for completed projects
• Guest user limits: 5x more guests on Premium
• IP allowlisting: restrict access by IP range
• 99.9% uptime SLA with credits

Side-by-side