Using the power scripts app , you can create issue template automations and solve this use case. You can bulk copy projects, issues, attachments and even create a template of issues to launch and reuse quickly. (more info)

We have jusst launched a new plugin for this, compatible from 6.3.6
Check and evalutate on: https://marketplace.atlassian.com/plugins/com.lbcg.jira.plugin.pro.BulkClonePro

Best
Lars Broden

I am also using the Zephyr for Jira plugin, and go through a similar process for Test Case Management. Cloning and moving test cases to a standard repository for future use (before archiving a project) is currently a very painful and manual process. A bulk clone feature would remedy this pain. It would also likely benefit other workflows such as potentially creating a standard set of tasks/sub-tasks, that could be cloned and applied component of work at any time during planning.

I am also using the Zephyr for Jira plugin, and go through a similar process for Test Case Management. Cloning and moving test cases to a standard repository for future use (before archiving a project) is currently a very painful and manual process. A bulk clone feature would remedy this pain. It would also likely benefit other workflows such as potentially creating a standard set of tasks/sub-tasks, that could be cloned and applied component of work at any time during planning.

We would find this feature very useful for our test team. We are using Zephyr and our work involves a pattern of very similar projects and test cycles. What we would like to do is to have standard test cases defined and held in the system (e.g. in a dummy Test Repository project) and then be able to find and filter them based on component, label or some such and then apply a bulk operation to clone them into the project where they are required. Having a "clone into other project" option under the bulk operations list would be exactly what we need for this.

BulkClone plug-in doesn't meet our requirement as it depends on a filter and not a custom selected issue list. It is not always possible to create a filter to select the issues we want to clone

Well,
You could always try out this free plugin: https://marketplace.atlassian.com/plugins/com.lbcg.jira.plugins.bulkclone.BulkClone

Can anyone please comment on when "Bulk Clone" functionality is scheduled to be made available in JIRA? We are using JIRA version 6.0.3 and I don't see any mechanism to bulk clone JIRA issues and change only a field or two. I was hoping in Bulk Operations, just like Bulk Edit, Bulk Assign etc., Bulk Clone will be available too but did not find it

As a workaround, JIRA CLI will do this for download provided you have the Clone Plus Plugin installed - this is what allows you to change project and/or update fields other than the summary field.

--action cloneIssues --toProject "XYZ"  --description "Bulk clone example"  --search 'project = ABC and summary ~ "xyz-*"  '

For OnDemand, you can only clone to the same project and change the summary using the same technique. Since you can't install the plugin for OnDemand, you have to settle for the limited support available with the built-in clone action.

It would be great to have this in Jira Core - our organisation is timid about non-Atlassian plugins.

It should check out add ons on http://www.atlassian.com/licensing/ondemand#managingatlassianondemandsubscription-4
Lars

The BulkClone plugin sounds great, but it is not available for OnDemand. Would you be able to add it to OnDemand?

You can use the BulkClone free plugin on Atlassian Marketplace to accomplish this.
It is free of charge and can be found under; https://marketplace.atlassian.com/plugins/com.netent.jira.plugins.bulkclone.BulkClone

Cheers
Lars

I want to create "template" projects with checklists of tasks that need to be completed for each implementation of our software. A bulk clone option in OnDemand would make this so much easier.

Please include bulk cloning to jira core! Would help a lot. Thanks.

Andres,
BulkClone Issues only updating certain fields has been resolved from BulkClone Version 1.06
Kind Regards
Lars Broden

Voted. Any update on this?

somebody might find this useful - https://bitbucket.org/oktopuz/jira-bulk-loader

That is my way of eliminating cloning restriction by using text templates.

Please enable the feature of Bulk Clone in JIRA.

Hi Lars,

i find the bulk clone 1.0.5 plugin can not copy fix version ,affect version,environment field .they are empty..
the bug is serious...

Would love a feature to bulk clone, as it's typical in my organization for projects to have similar build issues – for example, when we are basically repeating work from one locale (.com) to another (.co.uk) to another (.it) to another etc.

Hi Lars,
It's my fault,i didn't create the "BulkClone" group.

now i have a test with the plugin ,and find that the plugin seems can not copy the comment,Due date or Resolved Date from the original issues?
the cloned issues lost comments,Due date...

Thanks

Hi,

You have probably forgot to create a "BulkClone" group and added the adequate user to that group (See screenshots on the Atlassian Plugin Exchange site)

It is not until you add the group and it's privileged users that the BulkClone option appear visible on the project portlet

If you have any further problems, also make sure your'e running the compatible version of BulkClone with your JIRA version.

BR

Lars Broden
 

hi,Lars Broden
i put BulkClone.jar to the directory: ..\Atlassian\Application Data\JIRA\lugins\Installed-Plugins\
and put all 3 of the ".VM" files in the directory path ..\Jira_Home_Directory\WEB-INF\classes\templates\plugins\jira\projectpanels\
and restart jira
but in the Project Browser,i can't find the "Bulk Clone Tab"

later ,i upload the "bulkclone-1.0.5.jar" via "Upload Plugin" on Plugins tab
but the "Bulk Clone Tab" still cann't find.

my jira version is 4.4.1,and the "Bulk Clone" plugin is 1.0.5

Lars ,can you help me with the problem?

Hi all,
A new version of BulkCLone is out;
Highlighted features are;
1- JIRA 4.4 compaibility
2. Possibility to attach a "Personal" label on your cloned set to easily identify your clones
3. Improved error handling and minor bug fixes
You can find it at: https://plugins.atlassian.com/plugin/details/38411

BR/Lars Brodén, Business Architect/Developer

Hi Lars Broden,

I can't find the plugin in page https://plugins.atlassian.com/search/by/jira. Can you check and send me a valid link?

Hui

As a result of the "cloned set" it adds the "BULKCLONE" value to the "Component" field. It does this for all parent as well as subtasks in the cloned set, in addition Assignee is changed to CurrentUSer(), this in order to be able to identfy the bulk of the cloned issues.

We are working on an updated version right now where Labels will be used instead of updating component+assignee fields. This will enable you to leave the core data untouched but still identify the cloned set by a label according to the convention "BULKCLONE"+Timestamp+CurrentUser()

We hope to be able to release this in a couple of weeks time. (compatible for 4.4 as well)

Stay tuned

BR/Lars

After installing the BulkClone plugin, issues that are ment to be visible in projects when you are not logged in to JIRA no longer show up. All issues are now hidden regardless of what settings you have for them. Are you guys able to update BulkClone to fix this issue?

Thank you, got it working now, playing arround with it for a bit

Rune,

You first need to add a filter in a "JIRA Conventional Way", i.e. through the issue navigator and then save the filter.
Once the filter has been saved, the URL gets an additional "Filter ID", copy then the whole URL (with the including filter id) into the BulkClone Filter input field, and then it should work ok.

BR/Lars Brodén

Hey,

I am trying to get this to work, but I am getting stuck on the filter
URL part as shown in this picture:
https://plugins.atlassian.com/server/1.0/screenshot/fetch/38422
I am trying to get the filter URL as described in this post for a
different topic:
http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro

How do I create a filter URL if it is not in the way as described in
the above post, it won't let me continue without entering one.

–
Mvh

Rune Normann Hamre
Overingeniør, SUAF-SO/USIT/Universitetet i Oslo

Kontaktinformasjon
Besøksadresse: Forskningsveien 3B, 0373 Oslo
Postadresse: Pb. 1086 Blindern, 0317 Oslo
Kontor: +47-22852487
Mobil: +47-48222141
E-post: r.n.hamre@usit.uio.no
http://www.usit.uio.no/suaf/index.html

On Fri, 22 Jul 2011 09:46:28 -0500 (CDT), "Elaine Gamble (Commented)

Thanks Lars - asking for a restart...

Elaine,

There is a README file in the download package that explains how to deploy it and set up the user group.
In addition there are also screenshots that shows you where to find things on the Atlassian Plugin Exchange page, https://plugins.atlassian.com/search/by/jira

Once everything has been set up you need to restart the server for the changes to take effect.

Cheers

Lars Brodén

Help - I downloaded this bluckclone plug in, but who do I trigger it? Thanks! Elaine

All,
We have today got approval by Atlassian on our Bulkclone plugin it is available for download (Binaries + Source) on Attlassian Plugin Exchange site: https://plugins.atlassian.com/search/by/jira

BR/Lars Brodén

The JIRA Command Line Interface 2.x can be used to solve many of these kinds of use cases. Some new enhancements make it easier. Bulk creating of multiple issues/subtasks either from scratch or via cloning is possible. For instance, we use a csv file based on a template, but various options are possible using replacement variables etc. Much can be done without scripting and more complex scenarios can be handled with minimal scripting. In addition, with a little bit of Confluence page scripting, you can provide trusted users the ability to provide a few parameters and load a template of issues. The soon to be released 2.1 version will also support the Clone Plus Plugin enabling more use cases.

Hi Lars,
Another interested user here! Have there been any furhter updates.
Thanks, Rob

It has been deployed at atlassians plugin exchange site and iam awaiting publishing appproval from atlassian.

/Lars

Hi Lars,

Like Rahman ask, is there any update on this plug-in? This is a plug-in that we really need, we considered making one our self’s but we simply do not have the resources atm for that. If JIRA decides not to distribute your plug-in via the main page, will you make it available for download in some other way?

Hi Lars,
Is there any update or valid links from where I can download your plug-in and evaluate? This plug-in seems promising to me and definitely will help us cloning issues.

Thank you.

It is most likely the case that it hasnt been "approved" yet internally by Atlassian, why your experiencing a invalid link.
One thing of clarification though, since I had some problems finding a easy way to upload the ZIP with the source code within the plugin exchange service itself, I was obliged to use an external cloud service to deploy the ZIP. Therefore the "Download" push button will not work, use instead the "Checkout Source" URL in the "Useful Links" section to download the ZIP file.

BR/Lars Broden

Re Lars Broden:
The URL you posted seems to be invalid.
Maybe it will become valid as soon as Atlassian did the qualification thing?

Let me also update on our Bulk Clone plugin:
I'm sorry to say that our plugin will probably not come open source any time soon, as our client apparently does not see the benefit of having a community around its plugin (aka "free" reviews and maintenance) – which is a pity, as they really seem to like the plugin. Open-sourcing would thus need some extra effort, which unfortunately has been pushed down on the to-do list at the moment...

Seems like Lars Broden was faster. Looking forward to checking out their plugin!
~Neels

Hi again,
We have today uploaded a "BulkClone" plugin on the Atlasisan Plugin Exchange site (Pending awaiting Atlassian's qualification), referenced in URL https://plugins.atlassian.com/plugin/details/38411
This utility is shipped in its entirety with source code and binaries, as an open source initiative. we have been running this plugin in our live envrionment now for some time with good results.
There is a readme file attached which explains the various setup steps adn also screenshots attached in the plugin URL.

Best of usage

Lars Brodén

Hi again,
We are actually developing a plugin inhouse to solve "Bulk Copy" issue since we are in urgent need for it,which I am happy to share with the community. It is right now undergoing final tests, but it is looking promising. The plugin works as follows
1. The apperance of the plugin is on the Project portlet adding a tab called "Bulk Clone, if a security group called "BulkClone" is setup with members in it (To ensure that not all users can do this)
2. The utility asks for a Filter URL with a request id (The URL Which you copy from your filter which contains the records you want to clone)
3. You can choose to include
a) "Subtasks" for all issues
b) "Attachments" for all issues
c) "Related Links" to all issues
4. The way you will be able to identify your cloned set afterwards works as follows;
a) The plugin will create a "BulkClone" component in the current project unless already existing and assigne the issue to this component value
b) The plugin will assign "Current User" to the cloned set

Stay Tuned

Lars

Hello JIRA bulk clone fans,

so far I have received 5 replies to my probing post above, all in the form of "yes, we would be interested. Kind Regards, <name>". I am currently busy with other things, but at least wanted to let you know that I have received some responses.

I'm not sure whether it is currently worthwhile for us (elego) to negotiate and maintain this plugin as an open source project – nor a commercial one, for that matter. For me personally, though, it feels weird to have a piece of useful software and not distribute it, at all. We've developed this plugin for an enterprise customer, who paid for it and is using it in a production environment. We've simply never negotiated a public release with said customer, and that is the status quo. You are (still) welcome to share your ideas on this situation at bulkclone@elego.de (same email as in above post).

Kind Regards,
Neels Hofmeyr
elego Software Solutions GmbH

Also adding that this would be a fantastic feature to have. Not having this feature is a huge work flow limitation for how I maintain my Jira projects and means a lot of wasted time and effort doing something which could be utterly trivial.

We are forever cloning and this feature would be of great benefit if implemented.

Hello all,

I'm taking a personal leap of faith by telling you that I have implemented a bulk copying feature for JIRA 4.2, for a specific commercial client of ours. I've been trying ever since to convince this client to go public about our plugin, since unfortunately we failed to anchor that possibility in the initial contract. Without promising any success, you may write to bulkclone@elego.de stating the extent of your interest in a bulk copying feature for JIRA – at this stage, I'm merely going to collect contacts.

Our plugin takes either a filter name or a list of selected issues via the issue navigator as basis, and lets the user select a target project and custom fields to reset in the newly created issues, among other things. It provides detailed info/warnings before carrying out the action and provides a fairly simple way to undo bulk copying actions.

Let me repeat that, at this point, trying to make the plugin public is a one-man effort, me being a convinced Open Source developer... I can't even tell you the name of the client.

But if we have a list of people madly interested in using the plugin, it gives me slightly more leverage to argue with. Write to above email address and hold your thumbs.

Kind Regards,
~Neels Hofmeyr
elego Software Solutions GmbH – http://elego.de

I agree with the previous comment. It sums up my opinion about this feature. It could unleash lots of potential uses, including Requirements and tests management. I'm surprised this issue is not implemented yet.
And if you can choose what kind of link you want to keep or break like this plugin : https://plugins.atlassian.com/plugin/details/4997 it would be ideal.

To reconnect to the earlier conversations about the importance of a getting support for a "bulk clone and copy" of issues must be one of the single most important features for Atlassian since it could knock out potential competition from Requirements tools like Contour or Test Case Management tools like Quality Centre and add an extra incentive to existing customers to stay with JIRA instead of looking at third parties handling this better. If a Bulk Copy/Clone (Notice the difference that there should be a "check-mark" option whether you want to preserve clone links or not) are implemented could then be saved against a specific version the baseline concept could be applied on requirements and test cases overlapping in concurrent projects. Further more re usability of generic test cases and requirements are then made easy by instantiating them in a "Bulk fashion" to a development project. I sincerly hope you will put some full attention into this tool limitation as will accelerate efficenty with the tool dramatcially and eliminate the need for additional tools

This feature would be very handy when using JIRA as a Test Case Management tool.

Also eager to get a Bulk Clone operation to use Jira as a TCM system. Currently looking into adding it as a plugin but not yet sure it's possible.

Any updates on getting this feature implemented in the near future?

Bulk clone would be a great plus. I still didn't try cloning a task with its subtasks, but I believe this is a feasible workaround, in my case at least.

I would like to have the bulk clone and move to another project at the same time.

What we need is not so much a "bulk clone" (although the effect is the same), but a way to generate a set of issues from a template. Templates then could be created from a set of existing issues. Mass copy from a very small "template project" might help too.

We use JIRA & Confluence during more than 4 years and like both tools very much. But, we really appreciate if JIRA team may develop the feature to do bulk clone. We need it to use for JIRA Test Management.

With Greenhopper we are using JIRA now for all our development projects. I have just had to manually clone 75 tasks/sub-tasks across each of 5 sub-projects (integration work for 5 accounting packages but tasks same for each). Export / csv import does not help because it does not recognise sub-tasks. Would have been really nice to have at least a bulk clone facility and a string substitution within the bulk clone would be great (Change the accounting package name in each task / sub-task summary field). I expect to be doing a lot of this in future

We also have the same issue of needing to bulk clone tasks. In addition to the option of adding attachments, it would also be helpful to do other bulk operations as part of the clone, e.g. make bulk edits to tasks when they get cloned over (due dates, version, summary, etc.). Oh, and the ability to choose whether or not to send e-mail notices would be nice as well.

This feature would make JIRA much easier to use as TCM tool.