We are using Deep Clone for Jira Cloud as a workaround to not having project templates. I have a business project that I've setup as a 'template' and have asked users to clone this when they want to use it to run a process. Mostly this works ok but the problem I'm experiencing is the epics/issues in the cloned project still link back to the original project (cloned from), we don't want this, and I've tried different configurations but the only way the project will clone all the Epics/Issues etc correctly (and in the right order) is to keep the 'Link to cloned Epic (if available)' ticked, if I untick this then the Epics and it's tasks/subtasks do not clone properly (i.e. the tasks and subtasks do not appear under the Epic, they appear as separate tasks in the backlog only). This is frustrating our users seeing the issues linked back to the original project and having to manually remove them.
Am I doing something wrong? Is there something I should be ticking or not ticking to ensure the clone is exactly the same as the original project without any links back to it?
Hello @Vai Cheung,
I am the product manager of Deep Clone for Jira. Could you please reach out to our support, so we could help you to solve your issue?
As you've mentioned you have to check "Link to cloned epic" to link the issues to the cloned epic. It would be great to learn more from you, why the current implementation is a problem for your team.
Thank you!
Hi Marlene,
The original project we are cloning from is acting as a template (this is workaround we're using for the lack of customised project templates in Jira Cloud) we therefore don't want the project cloned to link back to the original. Is there another configuration when setting the clone parameters to ensure there isn't a link back?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the same question - but what is the answer??
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community, @[deleted]
I'm sorry for answering so late. I must have missed your question, @Vai Cheung.
If you don't want to create a link between the original and the cloned issue, make sure to un-check "Add clones issue link" under the advanced options in the Deep Clone dialog.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.