much needed! please add it ASAP!

Can we please get this feature implemented? 

Yes, of course. This one has been open for quite long and still no progress... sounds like a basic need to clone issues into multiple destinations

Yes, it is really required to implement ASAP

We want it, too! Is it really that hard to implement?

Another vote. We want bulk cloning

Another vote for bulk cloning, please.

 Do it, do it!!

Adding in a 'yes, please' vote here. 

I mean, really guys? Not even that? Can this software be more annoying and tedious to use? That is a core feature - we are not getting payed to manually perform task other apps do in like 5 mouse clicks...

At this point i'm suspecting that you consciously omit important features to make market room for payed "add-ons" - i simply cannot find other explanation for it. Come on, we're all in software dev business, don't tell us that feature is impossible to make. 

Be better, please! We are bleeding workhours here!

Legendary Atlassian, 15 years in the making

Was very disappointed that only MOVE not CLONE was supported in the bulk options. I have to manually clone 15 tickets this morning, argh.

I can't understand why this feature doesn't exist yet. Should be a must for project management apps.

We want to change methodology in teams and for that we want to create a Scrum Project from a Kan Ban without losing the tickets the team was working with. Having the ability to bulk copy tickets would help spare hours of migration 

Would love if bulk copy of test executions could be implemented in Jira. That would make life of creating release testing dashboards so much more effective  

https://getsupport.atlassian.com/browse/GHS-231586

This is becoming more and more important to be able to manage complex cross scrum dependencies. As the industry moves towards API enabled µServices, we will see more and more situations where multiple scrum teams that own multiple µServices need to share some aspects of their platform services, which will need to infer central requirements to the applications 'using' those platform services.

Manually cloning a story to the 150 µServices that are going to be running on our platform is going to be hugely time consuming and difficult to track. It feels like this requirement could deliver almost a one click solution to these issues.

Please include this feature soon! Plugins like JSU for example cannot create a bidirectional issue link between source and target issue.

We are also interested in this feature.  We currently use the Clone Plus plugin, however it can only copy one ticket at a time into one project.  We have a frequent scenario where we have multiple projects built around nearly identical applications for different clients.  If we find a bug in one, it likely exists in multiple other copies of the project.  We need the ability to easy create a single bug ticket and simply make copies of it in all the projects it will need to be handled in.  Using clone plus to clone the bug into one project at a time for 20+ projects is not an option, that would take far too much time and effort.

It's extremely frustrating that Jira does not have built-in bulk clone functionality. An operation that should take a simple few steps now takes 10x the time as you clone each item individually, export and re-import, or perform other workarounds. There are several great plugins that do this that aren't very expensive, but in my case (and I'm guessing I'm not alone on this) require all sorts of organizational hoops to jump through to purchase and install. This seems like a pretty straightforward feature so why not implement it and make users' live much easier! 

In our business-free process, there are activities that are divided into about 30 separate tasks that are interconnected. We perform such tasks in many projects. What functionality can be used to generate all these tasks in new projects?

Is this being looked at, or are there alternatives available? We need to clone multiple tickets and right now it is just a misuse of time cloning each story individually? Trying to see if anyone has come up with some innovative ways, other than a paid add on or exporting/importing tickets.

Hello Team,

We are using JIRA v7.10.2 server version. Then how can I do bulk copy issues within or to a project.

Is there any plugin is available then please let us know.

Thanks!

Any news on this? Is this included in your backlog? What is planned date for implementation?

I want an epic with 20+ tasks and stories for each release we do. Are you telling me this is somehow impossible still? Here's another vote for Cloud implementation. We don't have a plug-in option, so please, understand that this is a high-value fix for users.

Currently Bulk Clone Professional offers you to Bulk Clone 1 issueType to 1 Target Project at a time using the JIRA Bulk Operations

If you have mutliple Issuetypes you can redirect them to different target projects.

However you can not Bulk Clone 1 IssueType into Many Target JIRA Projects in 1 operation. In this case a workaround would be to save the JQL Query as a filter repeat the Bulk Clone Operations to as many project instances you need if for. The settings between each Bulk Clone operation are saved, so the user does not need to go through all the specific settings once again

Check out the the descirption here: https://marketplace.atlassian.com/plugins/com.lbcg.jira.plugin.pro.BulkClonePro/server/overview

Yes, I also still need that as a feature. We are using the CLI plugin for this now, but it really should be a core function.

PLEASE implement this feature. As someone who manages multi-product, multi-team, multi-env coordination, I currently have no easy way to create multiple tickets and pass them out to all the applicable areas that need to do work. Currently, I use Clone++ to create one at a time, linking between my IMPL project and each team project. What would be AWESOME is if I had one screen where I can create a ticket and then be able to create multiple linked clones, sending them to many different projects (editing them if needed first). In our situation major requests come to the IMPL team, then I create tickets for IT, CM, DBA, QA, etc to complete one huge job. thanks !

Why hasn't this feature been added to Jira Cloud. It's SO necessary. Are there any alternates out there? Bulk clone doesn't work on Jira Cloud

Everyone nowadays, develops in at least two platforms... and most of the issues created in iOS, for instance, are the same need it to Android. This would be an awesome new feature!!

We have a standard set of Jira Tasks we need to copy to new projects for the purposes of Tempo timesheeting. So this feature would be great for that.

In my experience, engineers often have a common set of tests or a battery of issues they need to replicate regularly as part of their testing and documentation process.

Having a bulk clone feature built into JIRA would not only be useful, but it would make sense given that a Bulk Edit feature has already been implemented. Having a "bulk clone" would seem to align with this philosophy.

Our you could try out this plugin that will do the job: https://marketplace.atlassian.com/plugins/com.lbcg.jira.plugin.pro.BulkClonePro/server/overview

We run an event management system that starts with a master project plan with about 3k lines. We then roll-out many regions which all need the same project plan. So we need to clone the master time and time again with all the issues.

Until this is enabled we will not be able to use JIRA CORE - it simply is not fit for our purpose.

Bulk clone/move tool is a must for Jira. It should allow changing certain fields while completing the operation. In our case we have to manually clone same stories for different components in one epic (could be 20 stories, multiplied for 3-4 components) which is madness.

Even more elegant solution for our case will be to have a Post Function in the workflow which checks against certain conditions, making necessary changes to some fields and the clones the issue. So for example you are adding one story in the backlog with 3 components, when it moves to "Selected for Development", the post action will check for these components and clone it 3 times for each component.

Actually the best thing will be to have some kind of simple coding language in the Post Functions section, so you could do whatever you'd like

or your could try out our solution adressing this gap in Jira: https://marketplace.atlassian.com/plugins/com.lbcg.jira.plugin.pro.BulkClonePro

Lars Broden

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

If using JIRA for SW-Testing you basically have a project used as testcase library and other projects for the testcase execution.
You start defining your testcases (all in the testcase library projct)... Later you copy the testcases into the other testcase execution projects.
In this scenario a bulk copy functionality would be very handy!

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.

This feature would also be very useful for SAP AG.

We have different jira projects to organize the whole development and we need to clone and move multiple issues/backlog items between jira projects. Nice thing would if we could put an optional link "duplicates" for each cloned issue pointing to the original one.

Regards,
Hristo

Ditto for us, we have a standard set of stories with project tasks, release tasks, sprint tasks, and monthly tasks that we need to do. We currently have to clone each parent at the beginning of a project, release, etc. We've combined these where applicable into a template, but this isn't ideal as developers spend more time deleting things (tasks) they don't need. It would be very handy to clone smaller stories in a bulk operation.

However from a UI standpoint I'm not sure how this would work, I would like to clone these (multiple parent items) X times and put each one in Y different places. Where X and Y are user defined? When all is said and done perhaps doing a clone on each one individually may be just as easy...

In any case, I"ll vote on this issue if someone smarter than me has good ideas. Perhaps just the ability to clone multiple parents would suffice.

We also would like to request bulk clone and move of Issues.
Dear Atlassian,could you help us?

It is extremely crucial for us to be able to copy projects, components, versions, and issues.

We have installed the copy project which is ok, except that is does not copy issues. We have also installed a plugin to clone and move issues. It only allows bulk moving of sub-tasks (not bulk moving of parent issues), but relationships with components and versions for that sub-task are lost when moved.

Our setup is such that we need to create a new project for each show that we are working on. We do not want to recreate the versions and components each time. We want a standard set of issues that can be set up with each new show. How we can do this?

We very much need the bulk copy of the issues ...its a major roadblock in using JIRA for Testcase Management

We also would like to request Bulk COPY and Move of Issues.

Hi we are doing requirements documentation . We need to do bulk clones to be able to duplicate and link requirements between projects.

I'm surprised that Atlassian has not commented on this request. Is it because there's already a way to do this with JIRA? I'd like to know the status of this.

Ideally, entire versions (milestones) would be able to transfer with the copied items, and allow the project lead to specify due dates appropriate to the version before the issues are copied to the other projects.

If the options menu for cloning included a comma-separated list of projects, this would be perfect. It seems, however, that we'd need to be able to limit who has access to that ability through some sort of group management for our enterprise.

The functionality I'm describing cannot be performed right now with a simple "move" or bulk move operation. It requires that we can copy and move multiple issues to ONE OR MORE projects at the same time, and control who has that ability through group management.