Project cloning

[*Mike Kushnir]

Does anybody know if there's a simple way to clone a project in JIRA Cloud? Without using anything like Deep Clone plugin? I need an exact copy of a project with identical ticket creation dates etc.

[Trudy Claspill]

Hello @*Mike Kushnir 

Welcome to the community.

Can you tell us about the problem you are trying to solve with getting a clone that includes identical issue data down to creation dates? How much of the issue data needs to be identical, exactly? All dates and issue history, comments, issue links, ...?

Also, are you talking about a Team Managed project or a Company Managed project? A Business, Software, or Service Management project?

Are you talking about getting the issues created with the exact same issue keys, also? And if so, that would mean you could not be "cloning" it into your existing Jira instance/site.

Are you wanting to clone the project into your existing Jira instance/site, or a different one?

Are you wanting to "clone" the project configuration also?

What about agile boards associated with the project?

If you can tell us more about the problem you are trying to solve, maybe we can provide alternate suggestions.

[*Mike Kushnir]

We basically have a project used by 2 teams developing 2 different components. We now want to separate them into 2 dedicated projects in the same Jira instance. Our projects are Software, Company Managed.

My idea is to clone the original project and then filter out and bulk delete the tickets made by one or the other team.

I tried to use Deep Clone to copy specific issues to the new project but the ticket creation date is reset to the current date and it messes the whole ticket history.

[Trudy Claspill]

Create a new empty project with the same configuration as the first project. A Jira Administrator can do that by using the "Share configuration with existing project" option during the project creation process. There are a few things that are not shared:

• the user and user group assignment to Project Roles will have to be replicated manually
• Any Component values will have to be added to the new project manually
• Releases will not be copied to the new project. Those would have to be created manually.
• Agile boards will not be copied. You would have to create and configure those manually, if needed.

Then use the Move Issue feature to move the desired issues to the new project.

That will retain all the issue history, date values, most of the data, and links between issues, as long as the new project has an identical configuration to the first project. 

Links of issues to Releases will be lost, as Jira supports cross-project releases only through Advanced Roadmaps in the Premium subscription.

If you are using the Scrum methodology, the Sprint values will continue to show in the moved issues, but the issues may no longer show in the original project's boards because they probably will no longer be within scope of that board's filter.

I might be missing something in this suggestion, but I hope you find it useful.

[*Mike Kushnir]

Thank you, I'll give it a try.

[Jack Brickey]

In the true sense of the word there is no OOTB project clone feature. Much of what people are looking for when asking about project cloning is actually achieved via shared schemes, workflows etc. which is in place OOTB.