Why no project cloning function?

[Pat Flanakin]

Seems the Jira production teams keeps changing features of Jira which aren't the most value-added; however, a feature that would be a HUGE value add would be a project clone built into the software.

If Jira can allow cloning one task, why not all tasks in a project?  Using a 3rd party app doesn't make any sense and if you can access one, you are offered a trial.

So, we have been relegated to the analog approach of exporting a closed project then importing to a new project via CSV files.

It works, but with technological abilities available to Atlassian, you would think they would have already provided a project clone ability.

Am I missing it or do I misunderstand?  I'm open to learn here.

[Fabio Racobaldo _Catworkx_]

Hey @Pat Flanakin ,

there is an open suggestion for that purpose https://jira.atlassian.com/browse/JRACLOUD-79726 

Unfortunately, currenlty you can do that using a third part app or using csv export/import as you said.

Fabio

[Monika Ambrozowicz_Seibert_]

You're not missing anything @Pat Flanakin Jira Cloud doesn't have a native project clone function. The closest thing is the CSV export/import path you're already using.

I know that buying a 3rd party app is not your preferred solution but, unless I'm wrong, there aren't any other efficient workarounds. If you'd consider an app, I'd recommend Templating.app (full disclosure: I'm affiliated with the team behind the app), which is an all-in-one solution for creating work items, descriptions, spaces, subtasks and more types of templates. Rather than cloning a specific space, it lets you define reusable space templates. A Space Template sets up the Jira project configuration itself, and Issue Templates define the full set of epics, stories, and subtasks that should exist in any new project of that type. When someone needs to create a new project, they apply the template and get the full structure in one go - no CSV, no manual issue-by-issue cloning. It is free under 10 users. 

Having said that, if you only need a one-time historical clone, the CSV path is probably still your best option natively.

[Nikola Perisic]

Hello @Pat Flanakin 

You can't use the cloning feature, because it doesn't exist as native feature in Jira. What you can do is to make the space that needs to be cloned a template out of it, then when creating a new one, you can use that template. Also, you would need to bulk move the issues from one project to the another since copying also is not there as the native feature.

Deep Clone would be the app that you are looking for.