Automation rules
Automation for Jira is metered per plan, and global multi-project rules hit hard limits exactly when you scale.
What people actually say
✕Global and multi-project rule executions are capped — Free gets 100/month, Standard 500, Premium and Enterprise 1,000 per licensed user per month before rules stop firing.
Source: Atlassian — Automation service limits ↗✕When the limit is hit, all rules for that product stop until the next calendar month resets the counter.
Source: Atlassian — Automation limits vs usage ↗✕Standard's overall automation pool is 1,700 rule runs per month total, while Premium meters per user — both numbers are easy to blow through with cross-project rules.
Source: Atlassian — Jira pricing page ↗
Rules are plain TypeScript functions running on Inngest or a Vercel cron — no monthly run quota, no 'rule disabled at the end of the month'. Every trigger is logged with full inputs and outputs so debugging an automation is reading a function, not guessing which of seventeen rules fired.