You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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:
Jira Systems Administrator
2,387 accepted answers