When running the automation to clone an issue it creates multiple issues.

Karen Borba March 20, 2024

Every time I run the automation it creates 5 new tasks. I need it to create only 1.

4 answers

0 votes
Karen Borba March 20, 2024

I ran the rule and it created 5 issues. 2024-03-20_15-26-59.jpg

0 votes
Karen Borba March 20, 2024

2024-03-20_14-27-43.jpg2024-03-20_15-06-13.jpg

0 votes
Laurie Sciutti
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.
March 20, 2024

Hi @Karen Borba and welcome to the Community!  Can you provide some details or screenshots of your rule?  

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 20, 2024

Hello @Karen Borba 

Welcome to the Atlassian community.

To properly help you debug your Automation Rule we need to see your rule. Please provide screen images showing the entire rule and the details of each step.

It can also help us debug your rule if you share the content of the Audit Log for the when the rule executed and gave you unexpected results.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 20, 2024

@Karen Borba 

The information you provided indicates that the issue is only being cloned once by that Automation rule. What makes you think that the automation is creating 5 new tasks?

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 20, 2024

Hello Karen,

You said "I ran the rule and it created 5 issues".

However the rule is actually triggered, not manually run. The trigger is the transitioning of an issue to the Open status.

Screenshot 2024-03-20 at 6.07.17 PM.png

 

The sample you provided from the Audit log documents that when the rule runs it creates just one new issue.

Screenshot 2024-03-20 at 6.09.08 PM.png

 

Additionally, your rule will only create new issues if the Summary of the triggering issue contains specific text.

Screenshot 2024-03-20 at 6.10.55 PM.png

The issue you highlighted in your latest image don't show that same Summary text, and the issue keys that are visible don't match the issue keys shown in the Audit Log sample you provided.

So, those issues were not created by this rule.

 

If you think that a rule is creating the issues based on something you did to the issue you highlighted in the Open column in your latest image, here is what you can do to try to figure out which rule did that.

View the issue details for the issue you highlighted in the Open column.

On the right side of the issue details expand the panel named Automation.

Screenshot 2024-03-20 at 6.14.58 PM.png

 

Click on the Refresh button in the upper right corner of that panel. That will update the panel to show the Automation Rules that have recently been executed for that issue.

Screenshot 2024-03-20 at 6.16.32 PM.png

 

You may or may not be able to click the link for the rule(s) to see the details and execution history. That will depend on your level of access and the scope of the rule.

I suspect that if there is a rule executing against that issue and creating 5 copies of the issue, it is not the rule that you have shared with us.

 

If you want to share the details of the rule that was actually run, and the information from its Audit Log, then we can suggest next steps in debugging it.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events