Why no project cloning function?

Question

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.

Nikola Perisic · Answer

@Pat Flanakin different priorities in the backlog. Focus is on the AI currently, since everything has shifted to AI.

I have a Python script that does clone software and business projects, you can check it out here: https://bitbucket.org/nikolaperisic/jira-python-scripts/src/48f5b29fceea61e5e914ac85815fc69a001a1595/Clone%20Jira%20space?at=main

Pat Flanakin · Answer

Thanks for taking the time guys, but Atlassian needs to answer the question:  what are they waiting for to create this functionality?

I almost feel like I'm asking a question no one should ask.

And by the way, I got an email this morning asking me if my question was answered, but I cannot reply to Atlassian directly and say that it wasn't answered.

Monika Ambrozowicz_Seibert_ · Answer

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.