Hitting Close to Execution on multi-project comment replication

Troy_tb5ddp

Hi, 

My team currently has in place an automation that replicates comments between Jira service Management Cloud and Jira Software Cloud for escalated tickets. Our plan is Standard for both tools

 

Looking at automation limits, I got the notification we are close to hitting our limit. I realize after the fact that Jira counts execution limit when a rule is triggered, even if the conditions aren't met. When other teams comment on their tickets for their own work, it is triggering the automation

 

I attached how the automation is configuration between two projects (one project is in JSM, the other is in Jira Software)

Is there an alternative way to configure an automation to achieve this that would reduce the execution count Aside from manually commenting or upgrading to Premieum?

Mark Segall

Hi @Troy - The two most dangerous triggers for automation limits are issue transitioned and comment added.  Is your rule locked down for scope?  Meaning - Make sure this rule isn't simply a global rule with no further conditions... Only explicitly include projects that are impacted by this rule.  

Other than that, you may need to upgrade your licensing to Premium which provides considerably more executions.