Automation: LookUp Issues Action is Creating Hundreds of Tickets

Jeffrey Bistrong
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2022

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

[POPS-2] Week of Issue Summary - JIRA 2022-02-13 22-58-53.png

Automation - JIRA 2022-02-16 09-12-46.png

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

Automation - JIRA 2022-02-15 11-57-31.png

Automation - JIRA 2022-02-15 11-57-49.png

 

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

Automation - JIRA 2022-02-13 22-56-28.png

2 answers

1 accepted

2 votes
Answer accepted
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 16, 2022

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2022

after changing to the capital "I", i am now getting the correct output, but it is still creating a hundred or so issuesAutomation - JIRA 2022-02-16 10-30-01.png[POPS-225] Week of Issue Summary - JIRA 2022-02-16 10-29-12.png

Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 16, 2022

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)

image.png

Like Curt Holley likes this
Mykenna Cepek
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2022

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

Like # people like this
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 16, 2022

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2022

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

Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 16, 2022

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 ;)

0 votes
Mykenna Cepek
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2022

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2022

thanks, updated

Mykenna Cepek
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2022

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2022

Automation - JIRA 2022-02-16 10-12-05.pngAutomation - JIRA 2022-02-16 10-11-49.png

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events