Stepmeter for Jira · Demo report · Test site
Where this site's automation steps go
The report Stepmeter gives admins. A working prototype now builds it automatically from a live site. It reads each flow's structure and its run results, then shows how many steps did useful work, how many went to runs that did nothing or failed, what caused it, and what to change.
Data: the Stepmeter test site, 8 flows (a ninth, added after this snapshot, is left out). Step totals from the Automation Usage tab on 9 Oct 2026, 9:37 AM. Run outcomes from the audit log. Flow structure read through the Automation Rule Management API.
Flows, most wasted steps first
Steps that did the flow's jobSteps on runs that did nothing or failed
How the numbers are worked out
- Each trigger, condition, action and branch that runs is one step. Inside a branch or a scheduled search, actions count once per work item. This matched the Usage tab on 56 of 57 steps in the test site.
- A run counts as wasted when it stopped at a condition before doing the flow's job, or when its main action failed.
- Fixes are found from the flow's structure: a broad trigger followed by a filter, work done before a check, a search that touches every match every day, a flow that fails every time.
- Savings are what the same runs would have cost after the fix. Event-driven flows aren't projected to a month, because that depends on how often a site's work items change.
- A web request counts as 2 steps, whether it succeeds or fails. This was found by comparing a failing and a succeeding request flow on the test site.