How Deep Clone Helps Us to Increase our Productivity

[#1]

Hi Everyone,

In the spirt of Apptoberfest, I would like to share a little about why and how we use Deep Clone.

Our primary reason for using Deep Clone is because the app will allow you to clone the issue into another project and/or another issue type. The built-in clone feature in Jira will only clone the issue into the same project and same issue type. 

We have some automation setup that will also allow you to clone issues into other projects and issue types, so we primarily use Deep Clone for those functions in manual cases. 

Another reason we use Deep Clone is because it can clone Attachments, Links, and Comments. And we can keep or clear Epic links. The built-in clone function in Jira nor Automation can do that currently!

Also, while doing the manual clone, we can edit select fields to have different values from the card we are cloning if so desired. We can either immediately clone with the values in place, or click the Create and confirm issue and make field value changes.

One of ways we use the app is by placing it directly in a post function on a transition in a workflow. 

As you can see, we get a lot of value from the app and always great customer service from the good people at codefortynine. You can find out more about the app here:

https://marketplace.atlassian.com/apps/1218652/deep-clone-for-jira?hosting=cloud&tab=overview

Happy Cloning!

[Maggie Norby Adams]

Thank you so much for this overview @John M Funk ! Way to get into the spirit of the month 🎃🍻

[Alexander Bondarev]

Thanks for sharing, John! Sounds really useful 👍

[Sharon Tan]

I love that you combined cloning with a workflow transition post-function - so efficient! Way to save your teams some work. Thanks for sharing, @John M Funk !!

[Marlene Kegel - codefortynine]

@John M Funk, thank you so much for this article. This is such a great appreciation for us at codefortynine that you took the time to introduce your favorite features of our app.

[Stefan Kallus]

@John M Funk Is it possible to copy complete projects with this app? We have about 20 customers. We want to make for every of them a project for service desk. But the content is the same for all of them. but one customer should not see the jira tickets for the others. Or is there a better way to implement this?

[Marlene Kegel - codefortynine]

Hi @Stefan Kallus,

I am Marlene, the product manager of Deep Clone for Jira.

It is possible to clone company-managed projects along with settings, issues, components and versions.

Please note that there are some known limitations:

• Team-managed projects cannot be cloned yet. We’re waiting for Atlassian to provide the necessary interfaces. You can project manually and clone all issues using Bulk Clone afterwards.

• Cloning board configurations is not possible at the moment. See our workaround how to add boards after cloning the project.

• Cloning Jira automation rules is not possible at the moment. You can read more about sharing automating rules across projects in the Atlassian community.

[John M Funk]

@Marlene Kegel - codefortynine  - Thanks for jumping in!