Hi everyone! I’m having trouble with duplicating tickets in Jira and wondering if there’s a better approach. When I try to copy an existing ticket, I want to preserve all the key information like custom fields, connections to other tickets, and child tasks. The problem is that the standard duplicate feature doesn’t seem to work the way I expected. I always end up having to manually adjust things afterward which defeats the purpose of trying to save time. Does anyone have tips on how to properly duplicate tickets? Are there any add-ons or different methods that work better? Would really appreciate any advice from people who’ve figured this out. Thanks in advance!
honestly the easiest workaround ive found is using the issue templates if your admin has them enabled. create a template from your complex ticket then just spawn new ones from it instead of cloning. saves so much headache with broken links and missing field data that always happens with regular duplication.
Something that worked well for me was using the REST API with a custom script when I needed to duplicate multiple tickets regularly. I know it sounds technical but there are some decent browser extensions that make this easier without coding. The main advantage is you get complete control over what gets copied and can even bulk duplicate with modifications. However if you just need occasional duplicates, I’d suggest checking your field configuration scheme first. Many organizations have fields marked as non-copyable when they could be safely duplicated. Had our Jira admin review this and suddenly the standard clone function became much more useful. Also worth noting that Epic links and some automation triggers won’t carry over regardless of method used, so factor that into your workflow planning.
I’ve been dealing with this same issue for years and found that the built-in clone function actually works quite well once you configure it properly. The key is going into your project settings and customizing which fields get copied during the clone operation. Most people don’t realize you can specify exactly what gets transferred over. For custom fields, you’ll need admin permissions to set this up correctly, but it’s worth the effort. I also discovered that cloning works much better than using the duplicate option - they’re actually different functions in Jira. The clone preserves more of the original structure and relationships. One thing to watch out for though is that some field types simply can’t be duplicated automatically due to Jira’s constraints, so you’ll always have some manual cleanup regardless of the method you choose.