This article describes how to trigger Deep Clone from Jira Automation using a Deep Clone post function and a (global) looping transition, where the origin and destination statuses are the same (Recommended for Epic/Tree Clones).
You can also trigger Deep Clone using the Deep Clone Jira Automation action (Recommended for Single Clones).
.png?cb=7f5d35c6330380776ffc042f00040705)
This is how you can set up a Jira Automation with (global) looping transitions.
-
Add a global looping transition to your workflow.
-
Add a Deep Clone post function to the looping transition.
-
Create a new Jira Automation rule with an action that triggers the looping transition.
-
Click on “+ add regex to distinguish between multiple transitions to the same status”
-
Define a transition match with the name of your global looping transition (e.g. Clone), to make sure that the correct transition is triggered.
-
.png?cb=bb57474382994c48ffbd940a8e51e4b2)
Now you can trigger a Deep Clone via Jira Automation without changing the status of a work item.
Make sure that your automation rule doesn’t cause a loop that creates infinite clones. Work items that are created with Deep Clone can trigger automations of “Work item updated” rules.
-
Global looping transitions can be removed from the work item view by adding the condition “Hide from User” to the transition.
-
If Deep Clone and Automation overwrite each other, you could insert a ‘refetch work item data’ action immediately after the trigger in Automation for Jira. In ‘more options’ you can manually configure a delay which would solve your problem.