Atlassian is changing the way Jira and other Atlassian products measure Automation usage. From December 3, 2026, extra usage billing will apply when organizations go beyond their included automation step allowance.

Every executed trigger, condition, action, branch, or loop can count toward this allowance.

For organizations running a large number of automation rules, this makes automation consumption an important factor to consider.

What Does This Mean for Customers?

Customers with high-volume automation may need to monitor their usage and consider how different automation requirements are implemented.

For simple workflows, native Atlassian Automation remains a great option.

But what about requirements such as bulk updates, recurring scripts, complex validations, or custom Jira behaviour?

This is where ScriptFabric can provide an alternative approach for applicable use cases.

Use ScriptFabric for More Than Standard Automation

Instead of using a native Automation rule for every requirement, customers can use ScriptFabric capabilities for certain workloads and potentially reduce their dependency on Automation steps.

Some examples include:

• Bulk Operations – Update or transition large numbers of issues in a single operation instead of creating automation flows for repetitive changes.
• Scheduled Processing – Run recurring administrative or monitoring tasks on a schedule.
• Event-Based Processing – Respond to Jira events with custom logic.
• Workflow Controls – Apply complex validation rules when users attempt to transition issues.
• Dynamic Fields – Change field behaviour based on issue data or user selections.
• Custom Calculations – Generate or display information dynamically from Jira data.
• Proactive Monitoring – Identify issues matching specific conditions and trigger appropriate follow-up actions.
• Custom Jira Actions – Give administrators and users purpose-built actions for specific business requirements.

These capabilities give teams another way to implement Jira processes without relying exclusively on native Automation for every scenario.

The Cost Consideration

With usage-based Automation, the question is no longer only:

“Can we automate this?“

It is also:

“Which approach makes the most sense for this requirement?”

For straightforward automation, Jira Automation may be the best choice.

For high-volume, script-heavy, repetitive, or highly customized requirements, ScriptFabric can provide another implementation option—and can help organizations reduce their reliance on native Automation consumption where appropriate.

Atlassian’s move toward usage-based Automation makes automation efficiency more important for Jira administrators.

The answer isn’t to stop automating.

It’s to use the right tool for the right job.

Jira Automation can handle standard workflows, while ScriptFabric can extend Jira with scripting, bulk processing, scheduled execution, workflow controls, and customization.

More flexibility. More control. Smarter automation.