Jira Automation Usage: Steps per Rule, Measured

说明与用途

文章测量了 Jira 自动化步骤成本：即使是未激活和空运行也会消耗步骤，两个旧测试规则占月度使用量的 88%，导致意外费用。

问题

Jira automation steps are billed per trigger, condition, action, branch, and loop, but the exact cost per rule and per run was unclear, leading to unexpected high usage and billing.

结果

The study quantified step costs: a failed condition run costs 2 steps, a scheduled rule that finds nothing costs 1 step per run, branches bill per item, and if/else blocks bill per branch. Two legacy test rules consumed 88% of monthly steps, highlighting the need to audit and delete unused flows to avoid extra $0.50/1,000‑step charges.

工作流

• 1. Identify rule types to test (e.g., transition, scheduled, branch, if/else).
• 2. Create 11 test rules via the Automation REST API, disabling them initially.
• 3. Enable each rule individually, trigger it with REST calls, and disable after 45 s.
• 4. For scheduled rules, let them run every 5 min for 2–3 runs.
• 5. Record run counts and step usage from the Usage tab and audit log.
• 6. Compare billed steps per rule with per‑run component counts to validate measurements.
• 7. Analyze high‑usage rules (e.g., test rule copies) and calculate potential billing impact.

证据

A run that stops at a failed condition costs 2 steps.

来源

A scheduled rule that finds nothing costs 1 step per run.

来源

Branches bill per item.

来源

88% of our site's steps this month came from two copies of a test rule somebody made a year ago and forgot.

来源

Steps beyond the allowance cost $0.50 per 1,000, billed from 3 December 2026.

来源