Issue Summary

According to our Service Limits:

Rules scoped to multiple projects will be assigned to the product that has the highest monthly limit

E.g. Let's say you've signed up to Premium plans for Jira and Jira Service Management.. And let's say you create a rule that runs across all three

Global rules will be billed to the product with the highest automation limit.

Global and Multiple project scoped rules should count towards the product with the highest automation limit.

And it looks like it is counting towards the wrong product in some cases. For example the JSM Standard license instead of Jira Software Premium license.

Steps to Reproduce

1. Install the Jira Premium product and JSM Standard.
2. Program some automation rules with global scope to exceed your the JSM Standard license automation service limits.

Expected Results

As per the documentation, the Global rules will be billed to the product with the highest automation limit, in this case Jira Premium in case all JSM Standard executions are consumed.

Actual Results

The rules execution are counted towards the Jira Service Management Standard license breaching the limit.

Workaround

If the limit is breached, please reach out to support so it can be reset while a fix is implemented.