How to Move Jira Issues With Deep Clone
You can not just clone issues but imitate the native Jira Move feature with Deep Clone for Jira. There are multiple ways of achieving this, but it basically comes down to deleting the issue after cloning. This is doable manually if you only clone a single issue, but quickly turns impossible when doing a Bulk Clone or an Epic/Tree Clone.
To achieve this, you need to use the Incoming Webhook feature of Deep Clone to trigger a Jira Automation that will delete the original issue.
Create the Jira Automation to delete the issue.
Create a new Jira Automation rule with an Incoming Webhook trigger. You can already copy the Webhook URL here. We will need it later.
Add a FOR EACH branch > Branch rule / related issues > Linked issues and select
clones
under Link types.Add a Permanently remove this issue action to the branch.
Configure your clone to trigger the Jira Automation.
Under Advanced options, make sure the Add clones issue link between clone and original issue is checked. It’s checked by default. Also make sure the issue link is set is the
clones
link type, or the link type you use in the FOR EACH branch of your Jira Automation.Under Advanced options > More options, check the Trigger Jira Automation Incoming Webhook on the cloned issue. Then enter the URL you have generated in the Jira Automation Incoming Webhook trigger.
Clone 🍿
You can use this guide to delete issues after they have been cloned via a normal Bulk Clone, Epic/Tree Clone, or more advanced ways via Presets or Post Function Clone.
Contact us if we can help you with your use case!