Clone issues and create task

[Francisco Navarro]

Dear community,

I have a project B in which epics are created that are cloned from another project A. In parallel, in my project B I have an automation that creates tasks when a new epic is created, but it is not executed when the epic is cloned from another project. What could be the problem? How should I set up my automation so that it recognizes a new issue, even if it is cloned?

Thanks a lot!!

[John Funk · Accepted solution]

Hi Francisco,

If the Epic is cloned/created by an automation rule, then it is probably that the second rule does not have the box checked on the Rule details page to allow the rule to be executed by another rule. 

Check that box and update the rule and give it another try.

[Francisco Navarro]

Thank you very much!

I checked the box in the rule that should create the tasks and it worked perfectly!

Regards!

[John Funk]

Great! Glad that worked. 

[Trudy Claspill]

Hello @Francisco Navarro 

In order to diagnose why your rule might not be working we need som additional information. Please provide the following:

1. Screen images that show the entire automation rules. 
2. The details of the rule Audit Log from an instance where you didn't get the expected results. Did the rule get triggered and not produce the results, or did the rule not get triggered at all?
3. 3. Details of relevant steps in the rule like the trigger, conditions, and branches that determine whether or not the rule proceeds.
4. Also how is the cloning of the Epic occurring? Is that being done manually by a user or through execution of another automation rule?