Automation triggered by clone creation

[Kyle Whitton]

I have an existing rule setup in my main project that creates a clone of a request in another project. I am wanting to setup some automation rules in that secondary project that are triggered when the clone arrives. Is this possible?

The option that I thought would work was running when an issue is created. This failed as the issue is cloned not created so the rule wasn't triggered when the clone arrives. 

[Luka Hummel - codefortynine]

Hi @Kyle Whitton and welcome to the community!

It is indeed possible to trigger automation rules in the secondary project when a cloned issue is created. However, since the issue is cloned rather than created in the traditional sense, you'll need to adjust your automation rule to recognize this. One way to achieve this is by ensuring that your automation rule is set to trigger on issue creation and that it allows other rules to trigger it.

You also might find our app Deep Clone for Jira helpful, as it offers advanced cloning options that can be paired with automation rules for more complex workflows.

You can also trigger a Jira Automation on all issues cloned with Deep Clone via and Incoming Webhook, as described here.

[John Funk]

Hi Kyle - Welcome to the Atlassian Community!

Can you share the rule(s) that you have? Are you saying that the first rule does not fully execute and create the Clone as it should? If so, can you also whare the audit log for when it runs? 

[Mayur Jadhav]

Hi @Kyle Whitton ,

Welcome to the Atlassian Community!!

As Second automation will be dependent on first automation result you need to select check mark the check box. Open the automation rule >> Rule Details and mark the checkbox (check to allow other rule action to trigger this rule). See the attached screenshot.

Regards,
Mayur