Global Automations billed/counted to Service Management instead of Jira
Asked by Gena Urowsky:

I've been reviewing our automation usage and comparing with the article here:

<https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/>

But finding that my Global scope automation rules are being billed against "Jira Service Management" instead of "Jira" which has a much higher limit. As a result I've already hit the limit mid-month. Any ideas on how/why these automation rules are in the usage for "Jira Service Management"?

The highest automation limit I have is with Jira -- by far (we aren't really using the jira service management product a lot and/or have very few users with it). From reading the article linked above, these global rules should be counted "to the product with the highest automation limit".

I dug into the automation using the most in this area - It's a Global Automation, with a setup similar to the below

* When: Issue updated
* If: Issue matches JQL - limited project set, status, issuetype. \*I checked all these projects called out specifically and none are JIRA Service Management projects.
* Then: Edit issue fields

Thanks for your help!


Answers:
author: Valerie Knapp
body: Hi [@Gena Urowsky](/t5/user/viewprofilepage/user-id/2175383) , welcome to the Atlassian Community and thanks for your question!

This isn't something we as a community can really help with, not having access to your instance, so I have tagged Atlassian support in, who should be able to give you a hand.

Best wishes

comments: author: Gena Urowsky
body: Gotcha, thanks!


author: Trudy Claspill
body: Hello [@Gena Urowsky](/t5/user/viewprofilepage/user-id/2175383)

Welcome to the Atlassian community.

As Valerie indicated, we are a community of users, so we can't directly access your system and examine the usage ourselves. For that you would need to contact Atlassian Support directly.

However in regard to at least this one item:
> I dug into the automation using the most in this area - It's a Global Automation, with a setup similar to the below

*
  > When: Issue updated
*
  > If: Issue matches JQL - limited project set, status, issuetype. \*I checked all these projects called out specifically and none are JIRA Service Management projects.
*
  > Then: Edit issue fields

If none of the projects named in the JQL are Service Management project, then you might what to change the scope of the rule from Global to Project Type, and then select Software Projects as the project type. That should ensure that the rule execution is counted against the Jira product vs. JSM.

![Screenshot 2024-07-22 at 1.19.16?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/337139i96B51BD55CE38949/image-size/large?v=v2&px=999 "Screenshot 2024-07-22 at 1.19.16?PM.png")

comments: author: Gena Urowsky
body: Interesting - not sure if this is new or was there before; but good find. I've just switched this one to reflect Project Type = Software projects. For now it's still under the monthly usage / Jira Service Management, but perhaps that's the historic data.

This is a useful feature though and would limit my project filter as I've specified in the JQL statement! Thanks for pointing this out.


Tags: atl-esc

cloud

cloud-automation

jira-cloud