Automation rule limit

Question

Hi,

The automation rule limit use to apply only for Global Rules, but now it seems to be applying even for project specific rules. Do you confirm that?

I find this change very frustrating, especially when considering the global context when Atlassian every year raises prices and cuts features. This business model will not work well for you in the long term. You are forcing your clients to go look for alternatives.

Regards,

Luciano.

Bill Sheboy · Answer

Hi @Luciano Nunes De Lima

Yes, project-scope rules now count toward usage limits.

Here is the September 2023 announcement when Atlassian changed the packaging model for how usage is counted: https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update  With that change, some rule actions do not count as "usage", so read the information carefully.

And here is the current documentation regarding how usage is calculated and the limits: https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

Please note there are other limits which can impact rule usage: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

Finally, that usage documentation does not appear to include the changes to merge Jira Work Management (JWM) into Jira.  Based on other community posts, that merge will apparently reduce limits further for all license levels below Enterprise.

Kind regards,
Bill

Dan Breyen · Answer

Hi @Luciano Nunes De Lima I found this Atlassian Announcement from last September regarding the packaging models for Automation.  As of November 23, project specific rules are counted towards the limit

• Single-project, project type, multi-project, or global rules will count towards your limit.
• Actions (log action, create lookup table, create variable, refetch issue, and look up issues) don’t count toward your limit.

Hope that helps.