While creating a checklist issue its creating clone ticket too,why this is happened?

[mummareddy supriya]

I created an automation rule in Jira, to clone a checklist issue from one project to another when it matches with the Label "xyz" .when ever i'm trying to create a checklist issue in main project its creating clone in this project too.If any one know the reason please provide me the solution please .

[Clara Belin-Brosseau_Elements]

Hello @mummareddy supriya

If you're seeking for an easier way to clone issues with their checklists, you can try our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).

You can check our guide here.

You can try the app for free during 30 days (and it stays free under 10 users).

Kind regards,

Clara

[Wojciech Wardaszko]

Hi @mummareddy supriya

You indicated that you're on Jira Cloud, but the screenshot does not match what I know as the Jira Cloud Automation. Are you on Jira Data Center by chance?

Not that it makes much of a difference in this situation, @John Funk answer is most likely correct, but it may help you in future cases if you select the product accurately - the answers may differ greatly depending if it's on-prem or cloud.

Cheers!

[John Funk]

Hi Mummareddy,

It is probably firing because you have the trigger setup for when the Label changes, including creates. And since you are cloning the issue, it is technically changing the Label when it creates the clone - causing it to fire again. Maybe modify the trigger to not fire when the Label changes on create, and then try it again. 

[Jack Brickey]

Hi @mummareddy supriya , can you look at the logs to see if your rule is triggering twice on a single event? Also, check if you possibly have another rule cloning the issue. Finally check the history of the unwanted clone to see if there is a clue. Maybe adding a comment action on the newly cloned issue in your rule to assist in troubleshooting, e.g. include the trigger issue in the comment.

[Wojciech Wardaszko]

For stuff like that I recommend using the Log action instead of comments - it's easier to review the audit logs in one place :)

[Jack Brickey]

Yep that works too.