How do I create a ticket on another board based on using Deep Clone and Automation Rule
Asked by Carol Wesolowski:

Problem:

I have a Task ticket with several sub-tasks that I Deep Clone (in the existing project) that I want to create a new ticket in another project based on the newly cloned sub-task ticket?

Here is the latest version of my Automation Rule

![Automation rule.png](https://community.atlassian.com/t5/image/serverpage/image-id/288679iA2FDD6AFE43F08E5/image-size/large?v=v2&px=999 "Automation rule.png")

The audit logs shows that no actions were performed because the issues did not match the condition. The following is the history of the cloned task that I want to apply the automation so that it creates a new ticket on another project's board.

![History.png](https://community.atlassian.com/t5/image/serverpage/image-id/288680i064107764272B742/image-size/large?v=v2&px=999 "History.png")

Any insights are greatly appreciated. Thanks!


Answers:
author: Bill Sheboy
body: Hi [@Carol Wesolowski](/t5/user/viewprofilepage/user-id/5205704)

First thing, I am not using the Deep Clone addon, and so my suggestion is based on what I know about automation rules. With that disclaimer out of the way...

Based on what you show, it appears that addon does what I expect: it uses the REST API to clone the issue, and sub-tasks, one after another...which takes time.

And, there is a known issue with the automation rule trigger Issue Created: it can fire so quickly that the data for the issue is not yet available at the time the rule starts. That manifests symptoms like conditions / actions / branches not working as expected.

The normal work-around for that (regardless of addons) is to always add the Re-fetch Issue action after the trigger, slowing down the rule and reloading the data.

Putting those things together (and without seeing your rule's audit log), I suspect this is a similar timing problem. Please try adding the Re-fetch Issue action immediately after the trigger to observe how that impacts the rule execution.

Kind regards,  
Bill

comments: author: Carol Wesolowski
body: Hi Bill,

Ah, that was exactly my thoughts that the automation was firing before the conditions where meet. Appreciate the suggestion of the Re-fetch I did not know this existed.

\~Cheers, Carol


author: Luka Hummel - codefortynine
body: Hi [@Carol Wesolowski](/t5/user/viewprofilepage/user-id/5205704)

I'm Luka from [codefortynine](https://marketplace.atlassian.com/vendors/1213041/).

Depending on the way you are using Deep Clone for Jira, you could use Deep Clone to trigger the Jira Automation with an **Incoming Webhook** as described [here](https://c49.link/deep-clone-for-jira/docs/incoming-webhook). Be aware that this would trigger the automation on all cloned issues. You would need to add an IF-check, so your action only run on cloned subtasks.

Otherwise, you probably need to design the automation, so it only triggers on subtasks in the first place.

Let me know if you could achieve your goal with your automation.

comments: author: Carol Wesolowski
body: Hi Luka,

Appreciate the other option. At the moment I do not have the automation working to create a ticket on another board, but will have time to try this later today.

\~Best, Carol


Tags: jira

jira-cloud