- \n
- Jira Cloud is counting every automation trigger, condition, action, branch, and loop since September 2026. Allowance limits and extra usage billing both take effect on December 3, 2026.<\/li>\n\n\n\n
- The same 12-item Definition of Done costs 13 automation steps per Story as detailed subtasks, 2 steps as a checklist added by a flow, and 0 as a Smart Checklist for Jira <\/a>default checklist template.<\/li>\n\n\n\n
- You still need Jira Automation to add a checklist when your condition goes beyond what the template settings support. Even then, one Import Checklist Template action adds every item at once, so the flow still costs 2 steps.<\/li>\n<\/ul>\n\n\n\n
What Is a Jira Automation Step?<\/h2>\n\n\n\n
\n \n![\"\"](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png\")
Definition<\/span>\n <\/div>\n \nA Jira automation step is a single unit of an automation flow in Jira Cloud: trigger, condition, action, branch, loop. The trigger starts the flow, and conditions decide whether it keeps running. Actions perform tasks, branches create separate paths, and loops repeat actions within the same flow.<\/p>\n <\/div>\n <\/section>\n\n\n\n
Steps are also the unit Atlassian uses to measure automation usage.<\/strong> According to Atlassian’s automation usage documentation<\/a>, each step that runs counts toward your organization’s monthly step allowance. For example, a flow with one trigger, one condition, and two actions uses up to four steps per run.<\/p>\n\n\n\n
Why Should You Optimize Your Automation Step Usage?<\/h3>\n\n\n\n
Optimizing your automation step usage helps you avoid extra charges and stopped flows in Jira Cloud when limits run out too soon. Here are the key points of how automation is now metered:<\/p>\n\n\n\n
- \n
- Steps count even when nothing happens.<\/strong> A trigger that finds nothing to act on still uses a step. So does a step that runs without changing anything or hits an error in a misconfigured flow.<\/li>\n\n\n\n
- Complex flows no longer save allowance.<\/strong> Atlassian used to count rule runs, no matter how many steps a rule contained. Now every trigger, condition, action, branch, and loop that runs counts on its own.<\/li>\n\n\n\n
- No more unlimited automation. <\/strong>Previously, <\/strong>Enterprise plans included unlimited automation flow runs. Now all plans, including Enterprise, have a monthly step allowance.<\/li>\n\n\n\n
- Going over the allowance costs money.<\/strong> Extra usage is enabled by default <\/a>for most organizations, and Atlassian bills it at $0.50 per 1,000 steps from December 3, 2026. If you turn it off, flows stop when the limit is reached.<\/li>\n<\/ul>\n\n\n\n
For more details on the pricing changes and how they affect automation, including how to calculate your automation steps allowance, see our guide to Atlassian usage-based pricing<\/a>.<\/p>\n\n\n\n
How Checklists Save Automation Steps: DoD Example<\/h2>\n\n\n\n
Imagine your team keeps its Definition of Done on a Confluence page. Everyone agrees to it, and most of the time people follow it. Then two Stories reach review with no documentation and no code coverage check.<\/p>\n\n\n\n
So you decide to put the list where the work happens. Suppose every Story that reaches In Progress should carry the same 12 checks: code complete, code coverage, code quality, integration, security, performance, etc. Also, you want Jira to add them, not you or anyone else manually.<\/p>\n\n\n\n
You have three ways to do that. The goal is the same, but the automation cost is not.<\/p>\n\n\n\n
Option 1: A Flow That Creates Subtasks<\/h3>\n\n\n\n
Your first instinct is to use Jira\u2019s native capabilities. The most straightforward way is to automate adding a bullet list in the work item description. However, it’s only one step closer to the task owner than the Confluence page. There is no convenient way to assign individual bullets (such as peer review, documentation, acceptance testing, etc.) to different people, ensure granular status tracking, or gate the transition to Done until all DoD items are closed.<\/p>\n\n\n\n
\n \n Note<\/span>\n <\/div>\n \nJira has native checklist-like action items<\/a>, but if you try to add them via a rule, the description text will just show text with \u201c[ ]\u201d instead of a box to tick.<\/p>\n <\/div>\n <\/section>\n\n\n\n
So you choose another path: add DoD as a set of subtasks. You build a flow that creates one subtask per check when a Story moves to In Progress. One Create sub-tasks action can hold several subtasks at once, but only as long as each subtask carries only a summary:<\/p>\n\n\n\n
![\"Jira](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-26-1024x761.png\")
<\/figure>\n\n\n\nHowever, code coverage means little without the details, and some tasks may need specific assignees. So you add descriptions and assignees, and Jira splits each subtask into its own Create work item action:<\/p>\n\n\n\n
![\"Jira](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-27-1024x884.png\")
<\/figure>\n\n\n\nEvery action that runs is one automation step. Your 12 checks now cost 13 steps per Story: one trigger + attached condition, and 12 create actions.<\/p>\n\n\n\n
\n \n Note<\/span>\n <\/div>\n \nYou can add a separate condition after the trigger, but it will be counted as an extra step. As our tests revealed, a trigger + attached condition consumes one automation step.<\/p>\n <\/div>\n <\/section>\n\n\n\n
To stop anyone from moving the parent work item to Done with DoD items unfinished, add a native transition restriction. Open the workflow, select the Done transition, and add the Restrict based on the status of subtasks rule. Note that the user will see that the transition is restricted, but you can’t add a custom message explaining why.<\/p>\n\n\n\n
![\"Jira](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-25-1024x600.png\")
<\/figure>\n\n\n\nOption 2: Setting Up the Default Checklist Template<\/h3>\n\n\n\n
Adding subtasks is a straightforward native way for granular requirements management in Jira. But over time, you face the downside: this approach clutters your board and increases management overhead. In some cases, it\u2019s better to use a checklist in a work item instead. This is what Smart Checklist for Jira<\/a> by TitanApps offers.<\/p>\n\n\n\n
While a checklist item isn’t a separate work item, it can include extra information: an assignee, a status, a due date, and more. You can also make it mandatory to gate work item transitions, which is especially useful in the DoD scenario. To learn more, read our article Jira Subtask vs Jira Checklist with Examples<\/a> or watch the video below. <\/p>\n\n\n\n
- Complex flows no longer save allowance.<\/strong> Atlassian used to count rule runs, no matter how many steps a rule contained. Now every trigger, condition, action, branch, and loop that runs counts on its own.<\/li>\n\n\n\n
- You still need Jira Automation to add a checklist when your condition goes beyond what the template settings support. Even then, one Import Checklist Template action adds every item at once, so the flow still costs 2 steps.<\/li>\n<\/ul>\n\n\n\n