Jira Work Management Automation rule executions are not counted towards the product with the highest limit
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
According to Atlassian documentation How is my usage calculated?
Jira Work Management Automation executions for instances with integrated Jira Work Management licences should be counted against the limit of the product with the highest execution limit.
- Suppose you have a Jira Software STANDARD License with 1700 rule execution (User Count 10) and Jira Service Management STANDARD License with 5000 rule executions(User Count 10).
- You created 5 Jira Work Management Rules and Saved them. These rule executions will be counted towards Jira Service Management as that has the highest execution limit.
- You Upgraded Jira Software to PREMIUM License which provides 10000 rule executions based on the 10 users * 1000 Rules. Now we have 10000 rule executions for Jira Software and 5000 Rule executions for Jira Service Management.
- Based on the above documentation, the Jira work Management automation rules need to be counted towards the Jira Software as it has 10000 now. However, that is not the case. The Jira Work Management Automation rules are still counted towards Jira Service Management's 5000 rules.
Environment
- Jira Cloud - New Automation Packaging Model
Cause
The product with the highest limit is calculated on rule save, not on rule run. So if your highest limit changes (e.g. due to an upgrade/downgrade), the rule’s “billing home”(Product) will not change.
On Rule Save: This means either Toggle the rule OFF and ON OR Edit the rule if needed and re-publish.
Solution
There are 2 ways to solve this.
Disable then Re-enable the rule, OR
Change the rule’s scope.
Last modified on Nov 24, 2023
Powered by Confluence and Scroll Viewport.