Summary

With the new packaging model for automation, each Jira product has their own limit. Global automations ideally count towards the product with the highest limit, and respond to subscription changes.

In certain situations, automation rules may count towards the incorrect product's limit.

Steps to Reproduce

1. Create a global rule (or a Multi-Project rule that spans multiple products)
2. Change a product subscription in one of the following ways:
   1. Either subscribe to a new product, causing a new highest limit, OR
   2. Unsubscribe from a product with the current highest limit, OR
   3. Upgrade/Downgrade a product edition or tier, in a way that changes your highest limit
3. Notice that the automation rule still counts towards the same as before product, even though there is now a different product with a higher limit.

Desired Results

Limits are counted towards the product with the highest limit, even after subscription changes.

Actual Results

Subscription changes don't cause any changes to which products that existing automation rules are billed against (i.e. the "Billing Home"). 

Workaround

Option 1 (single rule): Disable and then re-enable the rule (which will force recalculation of where that rule is billed to).

Option 2 (all rules): (If they're a large tenant with many rules that need recalculation): Escalate to Atlassian Support.