Import your Jira Automation rules export, rank rules by estimated step cost, and get risk flags and rewrite tips to cut usage.
Jira Cloud plans meter Jira Automation usage against a limit, and Atlassian is moving to step-based usage. A few rules with broad triggers, branches or loops can quietly use most of the allowance, and Jira doesn't tell you which ones before it happens.
All rules on your site draw from the same usage allowance. When it runs out, automations that teams depend on can stop running.
Branches and loops over related issues multiply the steps a single run uses. High-volume triggers like "Issue updated" multiply them again.
Usage reports show what already happened. The analyzer reads rule structure so you can spot expensive patterns and fix them first.
In Jira, open Automation (project or global), choose … → Export rules and save the JSON file.
Open the app from Jira settings and drop the file in or paste the JSON, then click Analyze rules.
See rules ranked by estimated steps, open any rule for risk flags and rewrite tips, and track changes over time.
Clear estimates, plain-language risk flags and concrete rewrite tips, all inside Jira.
Paste or drop your Jira Automation export and see every enabled rule ranked by estimated step cost, with totals and risk badges at a glance.
Open any rule to see why it is expensive (loops over related issues, high-volume triggers) and get concrete rewrite tips to lower its step usage.
Every scan is saved on your site. Scheduled digests compare your latest scans so you can see when step cost or high-risk rules go up or down.
Export, import, rank, fix and track, narrated step by step.
Narrated demo with captions (2:10). The app ranks a sample export of 7 rules, explains the top rule and runs a digest.
The analyzer is a native Atlassian Forge app. It runs on Atlassian's infrastructure, and Clearstep doesn't operate any server that receives your data.
Native Forge app that runs entirely on Atlassian's platform and uses native Forge authorization.
Your rules export, scans and digests are processed and stored in Forge app storage on your own site. Nothing is sent outside Atlassian.
Only two scopes: read:jira-work and storage:app.
Report a security concern to security@clearstepsapps.com.
Read the Privacy Policy for details on what the app stores and how long it keeps it.
Jira Cloud admins and Automation owners who want to keep Automation usage under control. Installing the app requires Jira Cloud admin access, and it's available in Jira settings once installed.
The app analyzes the Jira Automation rules export (JSON) that you export from Jira and paste or drop into the app. It reads rule structure (triggers, conditions, actions, branches and JQL) to estimate step cost. The app requests the read:jira-work and storage:app scopes.
In Forge app storage on your own Atlassian site. Scan history and digests keep the last 20 entries, and uninstalling the app removes all stored data. See the Privacy Policy.
No. Estimates come from static analysis of rule structure, not Atlassian's billing data. For actual usage, check Automation audit logs or Atlassian Admin insights.
Email support@clearstepsapps.com. We aim to reply within 1 business day. The Support page lists what to include and answers common questions, and the Documentation covers setup and how estimates work.
Install from the Atlassian Marketplace and run your first scan in minutes.
