I would like to duplicate Jira tickets between Projects. I do not want to move them. I know how to move Jira issues between projects and clone Jira issues within a project. I want to clone or copy between projects.
Hello @Matthew Cozzi
I don’t know if you found a solution to your problem but if not, I suggest trying our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).
You’ll be able to clone your issues across projects (and even sync them together if needed).
You can check the guide here.
The app is for free during 30 days (and it stays free under 10 users).
I'm Luka from codefortynine 👋
I would like to add that our app Deep Clone for Jira might be exactly what you are looking for. Deep Clone for Jira allows you to Bulk Clone and move multiple issues at once. It is designed to make the process of duplicating issues, including their sub-tasks, attachments, and comments, as seamless and efficient as possible. Deep Clone could provide a more automated and efficient way to manage the cloning of issues between projects compared to the manual methods mentioned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Matthew Cozzi
Are you willing to consider buying a third party app to get the ability to select a destination project when you select the Clone option? If so, I know of at least one app that provides that - Clone Plus. There may be other apps that provide that capability.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The only way I know how is to clone the Jira issue in Project A. And then move that cloned Jira issue from Project A to Project B. By cloning, a link between the original Jira issue in Project A and the cloned Jira issue in Project B is created prior to the move.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Matthew Cozzi ,
You would need to clone those issues and bulk move the clone issues to the other projects. There are marketplace add-ons out there where you make a project template with a predefine set of issues and make a copy of that for a new project.
Hope this helps.
-Ben
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Ben!
That helps...it aligns to what I thought (and did) but was hoping for a more elegant and more automated method.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You welcome. There isn't a direct way but now that you mention automation...you may be able to configure this operation if you have something like automation for Jira. It is included in cloud paid subscription.
Basically, you can configure a manual trigger automation which can clone and then take the next action to move the ticket. however, it may not be reliable, if the automation user is does not have all the right permission in both projects.
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.