Automation: How to prevent duplication of description field when Cloning

Luis Villamizar March 20, 2024

Hi All,

I've an automation rule that automatically populated the description field. 

However when cloning, the rule is triggered and description field is populated again causing duplication on the cloned issue.

Is there a way to prevent rule from being triggered in this scenario? 

1 answer

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 @Luis Villamizar 

There is not a separate Trigger for detecting that an issue is created by Cloning, so no, you can't prevent the rule from being triggered when an issue is cloned.

Do you only want the rule to populate the Description field when that field is empty? If so, you could add a condition to confirm that the field is empty before the step to populate it.

Screenshot 2024-03-20 at 8.06.50 AM.png

 

Another option is a check to confirm that there is not a Clones link for the newly created issue.

Screenshot 2024-03-20 at 8.09.14 AM.png

 

Bill Sheboy
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 @Luis Villamizar 

Yes, and...as a variation to the first method Trudy suggests:

You could add a condition to check for your Description text being present..

For example, let's assume your rule was adding this text to the start of the Description:

Business Problem: <add your problem>

{{issue.description}}

Your rule could check if the Description contains that template text before trying to add it again.

Kind regards,
Bill

Like Trudy Claspill likes this

Suggest an answer

Log in or Sign up to answer