Automation: LookUp Issues Action is Creating Hundreds of Tickets

[Jeffrey Bistrong]

With a scheduled event I am going multiple Lookup issues and then placing the lookup.size into a variable. I am looking to do an automated ticket once a week that reports out the the count of issues. 

The final output is outputting this and also creating hundreds of tickets

This is what each lookup looks like and then below is the variable. 

This is an overview of what the automation rule looks like as well as the final "create issue" which is creating hundreds of tickets

[Stefan Salzl · Accepted solution]

Hi @Jeffrey Bistrong ,

I just checked your "set value" action. I´m not quite sure if smart values are case sensitive but I know the lookup issue smart value in camel case {{lookupIssues.size}}. -->capital "I" for issues

Could you try this and maybe also add a "log action" after the "set variable" to see if the variable was set corretly.

Best
Stefan

[Jeffrey Bistrong]

after changing to the capital "I", i am now getting the correct output, but it is still creating a hundred or so issues

[Stefan Salzl]

Could you please provide a screenshot of your trigger settings?

The reason for my question is the following:
I tried to re-build your rule in my site. When I add the "scheduled" trigger in combination with the "re-fetch" action Jira forces me to add a JQL (to which the "re-fetch" could then refer) within the trigger. And with this set the action is executed for all issues of the result (see screenshot)

[Mykenna Cepek]

Nice catch, @Stefan Salzl. Almost certainly the "Run a JQL search and execute actions for each issue in the query" option is erroneously checked.

[Stefan Salzl]

Thank you very much @Mykenna Cepek  . Highly appreciate and feel honored by getting such a feedback from a community leader :) 

Let´s hope we caught the right thing ;)

[Jeffrey Bistrong]

yes, thank you unchecking it did the trick!!! thank you so much for helping me get to the bottom of it

[Stefan Salzl]

Awesome. Glad to know it works now. Thanks to all of you in this conversation for your effort to find a solution :)

happy automating to you guys ;)

[Mykenna Cepek]

Your screenshot ends after the third "And create variable" component. So we can't see what your rule looks in the vicinity of the "Create issue" component.

Please post a screenshot of the bottom half of your rule (so we can see ALL the rule components). 

[Jeffrey Bistrong]

thanks, updated

[Mykenna Cepek]

Ok. What does your Audit Log for this rule show? Can you screenshot both the overview (all recent runs and changes for this rule) as well as the details for the latest execution?

[Jeffrey Bistrong]