How can I lower my automation executions?

[Jean Dupree]

I am on Standard and have created a rule that uses issue created as the trigger and then has a specific condition that needs to be met for an action to occur, that action being to create an issue in another project.

Because I am creating an issue in a different project, the rule's scope is considered multi-project, and every execution counts against my monthly limit.  I have run out of rule executions because my rule executes EVERY TIME an issue is created, even if the condition is not met.

How can I limit executions to only those issues that meet the condition and not EVERY issue creation event?

[John Funk]

Hi Jean, 

Did you try the rule without including the second project? You should be able to create the rule in a separate project but still leave the rule as a single project (the project the rule runs in to begin with). 

[Jean Dupree]

Hi John,

I am sorry but I don't understand what you mean.  How can I keep it as a single project?

Also is there any way to include the condition in the trigger to reduce the number of executions?  

[John Funk]

Yes, just try to run the rule as a single project rule - only citing the triggering project. But then go ahead and create it in the second project and see if that works for you. 

No, there's not a way to do that real time with the trigger. You could do a scheduled trigger and run it once a day or a few times a day if immediate changes are not needed. The other option is to create a custom field and populate it with a post function in your workflow as issues transition. Then base your trigger on that field changing instead of the transition.