Do Global Automations that do not do anything on JSM Projects still count against JSM Totals?

[Mark Williams]

We are running into an issue in the last 60 days where we are running over our Automation limit for JSM projects only.  However we only have two projects that JSM projects. 

My questions are:

Do Global automations that do not make any updates or changes to JSM projects count against the JSM total?

Is there a way to see exactly what automations are running against our JSM count? 

Is there a way to see which project is causing the count to go up so fast?

Mark 

[Ajay _view26_]

Hi Mark,

You should be able to see the split of the usage based on rules at the below link - 

https://<instancename>.atlassian.net/jira/settings/automation#/tab/usage

[Mark Williams]

I have looked at that and I am confused. The only rules that are running are the ones that are Global for Jira Software projects. They do nothing against the JSM projects. So, with that being said ALL Global automations whether they do anything to a JSM project or not ARE counted against our total.

Mark

[Marc - Devoteam]

Hi @Mark Williams 

Global rules will be billed to the product with the highest automation limit, if in you case this is JSM?

Then yes the global automations count towards the JSM limit.

[Mark Williams]

Our JSM is being billed at Premium with a limitation of 100,000 automations. Our Jira Software/Work Management is on Enterprise with no limit.  

For the first time last month, December, we hit our max for JSM automations on December 28th. This month we are about to hit our limit in the next day or two. When looking at usage, we only ran 1981 automations from JSM.  However, we ran way more than that for Software/Work Management.  

I did find a way to change from Global to Project Type.  However, that feature is limited to one type of project type. I really need to be able to choose two project types. If I can get that updated to choose two types, I think that will correct my issue with Global automations.

Mark

[Marc - Devoteam]

HI @Mark Williams 

That is not an option, wouldn't it be better to set the scope of the rules to the projects related.

And are all rules needed?

Are there actions that could be set in the workflow for example?

[Mark Williams]

Unfortunately, we have 3 JSM projects versus 314 "other" projects.  Listing all those projects to avoid 3 is not worth the hassle. I would rather be able to exclude 3 projects from the global.

Is there a way to exclude projects from the Global choice? From what I have been to find there is not a way.

Mark

[Marc - Devoteam]

Hi @Mark Williams 

No this can't be done.

You only have an include option in an automation.

But then run the rule only on all project types, except Service Management projects

[Mark Williams]

Hi Marc,

I do not understand you response. You say it cannot be done to exclude JSM projects and then you say if can be done.

I am confused.

Mark

[Marc - Devoteam]

Hi @Mark Williams 

Set your automation rule scope to option Project Type select all project types except "Service Management Projects"

Then the rule should run on all projects except JSM projects.

[Mark Williams]

I have tried to do the Project Types multiple times. It only allows one choice. If you know of another way to have all project type but JSM, please fill me in so I can do this.

Mark

[Marc - Devoteam]

Hi @Mark Williams 

Answer, DAMN!!!

The only option to have is to clone the rule and set each rule for a Project Type

[Mark Williams]

I already put a ticket in with Atlassian to see if we could get that as a feature request. It would seem that a lot of companies would benefit from this feature. 

We will see what Atlassian says. I plan on talking to them at Teams 25 about it as well.

Mark