Automation rule limits (Standard VS Premium)

[Travis Alexander [Empyra]]

According to some Atlassian-published documentation, it would seem that, within the JSM Standard product, users can't configure cross-project/global automation rules. However, in my experience, they can-- with a 500-run limitation, per product. Whereas premium is unlimited.

Assume I had JSM Premium and Jira Software Standard, and I had automation rules creating issues from JSM projects into Software projects-- which product's count would this go against (JSM or Software)?

[Dirk Ronsmans · Accepted solution]

Hi @Travis Alexander _Empyra_ ,

This is explained in detail here:

https://support.atlassian.com/jira-software-cloud/docs/how-is-my-usage-calculated/

For your specific use case "create issue" there is even an exception:

One exception to this is the cross-product Issue create action. For example, if you want to create an issue in Jira Software based off an event in Jira Service Management – this will count as a single-project rule, not a global rule.

If you do use global rules they are counted per user on premium (even tho they can be executed by any user (so not specific to a user, more like x amount of users gives you x times 1000) for standard and free you are limited to 100 or 500

Since single project rules should be unlimited even in the standard plan.

https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

[Travis Alexander [Empyra]]

Thanks, @Dirk Ronsmans

I think some of my confusion has been around the terms "cross-project" and "global".   Are you using these terms synonymously?  In other words, whether the rule is configured within the project or in the global settings, the same applies-- it's simply counting rules that potentially impact multiple projects. 

Or is there some distinction? 

Thanks, again!

Travis

[Dirk Ronsmans]

Imo global and multi project are the same. 

The moment a rule impacts multiple projects it becomes a global or multi project rule. (With the exception of that create issue use case mentioned)

[Travis Alexander [Empyra]]

Right.

Well, you've been very helpful.

I suppose I am still just wondering what would happen if someone had JSM Premium, and Jira Software Standard and, ignoring the Create Issue exception, had global rules configured that potentially impacted both Jira Software and JSM issues. JSM has a ton, but Jira is limited to 500. Would they just stop working for Jira Software and continue executing on the JSM issues?  Or would all cross-project rules just pull from a pool of whatever the total number is? 

Believe it or not I have a customer in this situation and it makes my head spin.

Anyway, don't feel obligated to figure that one out. Ha!  I think I'm well enough equipped to speak to this. 

[Travis Alexander [Empyra]]

Ah, nevermind.  Found it.

"Premium users have 1000 global and multi-project rule executions per paid user per month. Ex: 200 users in Jira Cloud Premium will have 200,000 monthly global/multi-project rule executions per month. This is pooled across all Jira tools and all users. Enterprise users have access to unlimited automation executions."

[Dirk Ronsmans]

Yup, the amount is based on users and plans but they are all pooled so one big heap that just gets consumed :)

[Jimmy Seddon]

Hey @Travis Alexander _Empyra_

I don't know for sure, but my expectation is that it would count against the project for the issue that triggered the automation rule execution.

Just remember that if you have a multi-project rule, I'm pretty sure a rule execution counts if a trigger execution is considered.

For example, if you have a rule that executed on Issue creation.

Thanks!