Hi All,

We are currently tidying up our public JIRA instance so I will close this issue as we are tracking this request on the main linked issue: JRA-7020.

Cheers,
Roy

Thanks Gum Shoes!!

I've just installed the 'Copy Project plugin' from http://blogs.onresolve.com/?p=57. It works like a gem.
Does exactlly what I was looking for - which is just basically to create a new Project based on a 'Project template'.

I created a new Project category = ' Project Templates'
Created new - Project templates - eg, External Client Project Template & Internal Client Project Template.
configured the standard schemes / security / workflows etc.
added a standard list of Components, Versions etc

The author of http://blogs.onresolve.com/?p=57 has fixed it to work with 3.13.x now, it works again for me.

We have been using the http://blogs.onresolve.com/?p=57 plugin for JIRA 3.12.2 but it no longer works with 3.13.2.
Has anyone had any luck using Jelly for this?

So here are my IMHO thoughts inline on the questions Jeff poses above:

What would cloning projects involve?
Cloning projects allows users to utilize JIRA in a application lifecycle management sense in that they can determine what feature items can be associated with typical "project" that parallels their SDLC to some extent. Each release cycle can automattically generate a "basic project" or template with all the typical issues automatically populated with default values that can be customized based on what is going on in the next release. This would help us in terms of software release where the development is more like an assembly line such as in information systems related to clinical research orgs (CRO). Same basic software is released multiple times for multiple clients, some with customization some not.

• Cloning just the project info (obviously the key would need to change)
  At the very least the project info and base level issues. Perhaps a "batched, clone and move" event could create a fresh project from an existing "template" project. Perhaps maybe something more elegant if needed.

• Cloning associated permission, notification, workflow schemes?
  Make this configurable. Ideally perms, notification and workflow is abstracted somewhat from the project level objects so that projects could "subscribe" to perm, notification and workflow schemes already in existence, or possibly subscribe to new ones. The batch clone and move idea could potentially just grab what ever linkages exist in the template project if the user selects this level of cloning.

• Cloning associated custom fields?
  Make this configurable. Ideally custom fields are portable enough to be repository material that can be drawn into a particular project. The batch "clone and move" idea could potentially just grab what ever is in the template project if the user selects this level of cloning.

What are the problems that you're experiencing, that you think project cloning will solve?

Some of us want to be able to create an SDLC that is more like an assembly line VS. product leveling, or extension. So, more like banging out cookie-cutter versions of the same system with minor configuration changes vs a whole new version of an exsting product.

JIRA would be awesome to manage this, but needs to be able to repeat projects with base configuration without having to "hand create" the basic beginning state (by adding issues etc...) of the assembly line prior to a starting a new cycle.

We also DO REALLY need this feature. Please add it ass soon as possible.

We are in the process of evaluating JIRA. So far, it's been very promising, but I see this as the real stumbling block.

Our use of JIRA would be to track bugs and issues on a product we sell to various customers. The product or solution is in essence the same for everyone, and I had envisaged having a separate JIRA project for each customer installation. Now that I know we can link issues across projects, this would be a very efficient way of managing product bugs and issues which appear in every installation.

However, we would still need to set up each project individually, and we would like to have a kind of "template" we can apply so we can easily create the same components and versions across all projects.

I haven't researched workarounds, but would it not be possible to create the fields manually directly in the database? I don't like the idea of doing this as it looks scary to me, but I'm not a database expert (we are using SQL). I guess this could be done but would be unsupported?

So being able to rapidly clone "empty" projects would be the perfect solution and it looks like several people out there are requesting this feature.

I agree with Scott! Come on JIRA give us clone project, please
Clone Project should be standard – I tried the work around method that was suggested by Jira support , that uses an unsupported plugin , and it failed to work.

Dudes, this is really really sad that you cannot clone a project in Jira. We are wrapping up a project and moving on to a next-gen endeavor, we need to create a new project that has nearly 95% of the same components and users/groups, but apparently there is no way to simply create a clone of the project. There are 100+ components and 1000+ users/groups. Now we are stuck entering all these things in manually; it's an enormous time-sink for us, and prone to error. This can't be a feature that is terribly difficult to add, I added a "clone project" feature to Bugzilla in less than 3 hours, so come on, we shouldn't have to wait 2 years for something like this.

In addition to the the June Comment, I had the need to create another project identical to my other project with just the name of the schemes changed, and the users were different. I had to make a few adjustments to the custom fields, but the need to recreate each part in a sequence that was not familiar to me (because I had only done it once before many months ago) was so burdensome. Then because of one thing I forgot to do, it caused me 5 days of doing it over and over again to try to get my fields up in the new project. I even had a ticket open to try to figure out what was wrong. I solved it myself yesterday when I realized what I forgot, but cloning that project and just renaming each of the schemes, key, project, etc would have been so much easier especially for those of us that don't create projects very often.