Execute global rules only when all conditions met to limit the execution count

[Deleted user]

Hi,
Here is request for help.
I'm trying to optimize global rule execution counts in jira automation. (we use cloud standard and  limit per month is 500 executions)

I need to execute my global rule when issue transitioned "in Progress" of certain issues types only.

Right now,  it is getting executed whenever issue transitioned to "in progress" of any issue type and step two it is check condition on issues type and getting executed if condition passed - which is ok. Though I'm not processing any data..., this initial validation counting as one execution.

My idea is trigger global rule only if issue type of "issue" or "bug" and check this condition in a project rule so that global rule triggered only when needed.

How can this be achieved? help much appreciated.

thanks

[Jack Brickey · Accepted solution]

Hi Venkat, so unfortunately this is not possible. Automations are counted based up a trigger not on the conditions. :-(

This means if you have the Issue Transitioned as the trigger for global then EVERY transition will count as an executed automation. Options:

• consider a different trigger - likely won't fit your needs?
• consider Premium = increased cost
• consider implementing the global automation into every project where you have unlimited = could get tedious if many projects
• consider a different solution, e.g. post function for the specific issuetype workflow
• consider another addon = increased cost

[Deleted user]

Thanks Jack.

I'm exploring the options you suggested

Could you please suggest Add on good in this scenario?

thanks

[Jack Brickey]

I’m sure there are quite a few you could consider. Basically a scripting addon, e.g Scriptrunner, Power Scripts.