Hi all,
I have seen some discussions/questions about cloning a project. But they seem to be outdated. I want to clone a project completly (with its sub-tasks). How can I do that?
You will most likely need a add-in to achieve this in one bang.
Alternatively, you can use the standard shared configuration when creating a new project to clone the same project configuration and then use Automation to clone or create the issues and bring them over to your project.
If add-in's are off the table for you and your org, then automation is going to be your best friend.
I'm also looking for a solution. Is there any free add-in? And is standard shared configuration is in free plan available?
A Jira admin can create projects with a shared configuration in cloud.Here is the documentation for this case.I assume when nsuwps said he want to clone including Sub-Tasks the actual content is meant (for example an issue BOOK-4711, which is a Sub-Task, should be cloned to SHELF-4711, also there being a Sub-Task).This is not possible using "create a project using a shared configuration with another project".On Jira Server you have the option to clone a project including configuration & issues using Script Runner. I must confirm this option is not available in cloud for Script Runner.
Welcome to the community, @nsuwps ks.
We've just released an update for our Jira cloud app Deep Clone for Jira that enables you to clone entire Jira projects, including configuration, issues and sub-tasks.
To clone a project you simply select "Clone project..." as target project in the bulk clone dialog.
Don't hesitate to share your feedback with our support team.
Are the workflow statuses in the project also copied 1:1 or are all tickets set back to the starting status?
Hi @Noah Hofmann,
It is possible to clone the workflow statuses with Deep Clone for Jira.
Nevertheless you must keep some things in mind, in order to clone the issue status succesfully. You can read more about that in our documentation.
@Marlene Kegel -codefortynine- Can you also clone JSM projects? That would be really interesting !!
If cloning a Jira project is not a one-time operation but rather a repeated operation using the source project as a template, think of your project as a process.
Flower - Process Automation allows you to create a graphical process template (in BPMN) that can then be cloned as many times as you like. This process instance contains all the desired hierarchies, such as Epics, Stories, Tasks, and Sub-Tasks.
@Michael Da Costa Flower also supports team-managed projects
Take a look at why recurring projects are processes.
Hello,
There are two main things that one might want when cloning a project: to copy the project configuration or to copy its content (its Epics, Stories and Subtasks). Or both, of course.
Cloning the project configuration can be done with a native Jira feature, the shared project configuration.
However, in order to clone the full content of a project, I would strongly advice using an add-on such as our app, Elements Copy & Sync, to make your life easier.
It will let you clone the full content of your project (issues, fields, comments, attachments, forms, etc.) automatically, with no additional action required on your part, each time a new project is created. It will keep the hierarchy of your issues as well, meaning that Epics can be cloned fully, including their issues and subtasks, with the same structure in your new project.
The cloning of your project can be triggered in many ways, either manually, or with an Automation rule, or even from the Jira search result (if you need to pick and select which Epics you want to copy and which you don't).
As a bonus, the app lets you keep your projects synchronized. This is useful when your "source of truth" needs to be updated. You will be able to simply update the stories in the template project, and the changes can be automatically applied to all the projects that were created from it.
Elements Copy & Sync is free for 30 days, (and stays free if your instance is under 10 users), so feel free to give it a try, and don't hesitate to tell reach our Support if you have any question.
Kind regards,
Julien
Hi,
This is Majid @ Exalate. A few questions here please:
Thanks
Majid
Hello @nsuwps ks
using native Jira features, you can use the 'Share settings with an existing project' checkbox and select an existing project as template. This will use all configuration schemes that the current project (issue type scheme, workflow scheme...) is using, but not more.
What is missing, as you pointed out is the cloning of sub-tasks (issues) boards, components, version, issues, project role assignment, project description, project lead, default assignee and more small details. So without addon there will be a lot of manual tasks after the initial project creation
If you are up for third party apps, we've built Project Templates for Jira with the intention to cover those native limitations in cloning projects or creating project templates. You select one project as source and than specify what should be cloned. With issues cloning you have multiple checkboxes you can specify. You can decide if you want to save those project cloning configuration in a template to allow repeated cloning without much effort.
Please note that the app does not support team-managed projects or service management projects yet.
It looks like you're new here. Sign in or register to get started.
