clone Project with JIRA command line interface


How can I clone project with ALL schemes, roles, etc...?

I am not able to clone project with all schemes using one command in jira command line.


1) This command creates project from target with components, version, roles, notification, permission schemes, but issue type scheme and workflow scheme of created project are default!

jira --action cloneProject --project "Source" --toProject "Target" --name "Project from template" --copyVersions --copyRoleActors --copyComponents --permissionScheme "permission scheme" --notificationScheme "notification scheme" --issueTypeScheme "issue type scheme" --workflowScheme "WF scheme"

2)this command returns error:

parameter "project" can not be declared more than once

jira --action cloneProject --project "Sorce" --toProject "Target" --name "Project from template" --copyVersions --copyRoleActors --copyComponents --permissionScheme "permission scheme" --notificationScheme "notification scheme" --updateProject --project "Target" --issueTypeScheme "issue type scheme" --workflowScheme "WF scheme"

Is there any solution?



4 answers

1 accepted

I've just run into the same problem. I expected cloneProject to clone the issue types, workflow, screens, and field config with an option on the project actors, and (maybe) the issues. As in "I want a new project that works like existing project X" In our environment, the default schemes are what came with the product and we don't use them.

If Bob Swift is listening in he might like to comment on this.

An alternative is to use create project. This requires project (key) and lead, and, can set: name, description, url, defaultAssignee, permissionScheme, notificationScheme, issueSecurityScheme, workflowScheme, issueTypeScheme, issueTypeScreenScheme, fieldConfigurationScheme.

It's not as nice as a one-stop clone operation but you could set up some createProject scripts with perhaps some added copyActors operations.

Thanks Bob, you beat me to it.

I've created an improvement request: []. Add your votte

You suggestion to create a run script is good. It provides the most flexibility for creating a new project based on the current support. Under the covers, cloneProject does some of that, so either cloneProject, updateProject, and some other actions or just start from scratch with create.

0 votes
Mizan Community Champion Sep 02, 2013

You can also try Script runner plugin which provides a copy project feature .

  1. Those 2 schemes are not currently supported on the cloneProject action. You can open an issue for an improvement. In the meantime, just run an follow-up updateProject action.
  2. You have 2 --project parameters on the action, remove one of them.

Hi All

Thank you for advices, I think in my situation the best solution will be Script runner plugin, it provides the same action.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,998 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot