I think 20338ca9262c is right. There are innumerable use cases for a bulk cloning feature and it would be impossible to articulate them all.

ldeutsch I believe over the 10+ years this ticket has been open that there have been many examples of what we as users are looking for with this functionality. I feel that you asking this question is once again Atlassian stalling and Atlassian has no intention of giving the users what they are asking for. Atlassian is going to lose a lot of customers conducting business in this fashion and will earn a negative name for it as well.

ldeutsch , I think you are correct.

I can give another: handling insurance companies integration, for every new partner there is a set list of activities we must do, and it's basically the same uses stories and subtasks, just changed to a new project, and status reset would be nice.

Hi all, I would love to hear more about the problem this is trying to solve - mainly because cloning in bulk may not be exactly how we would solve it.

My understanding from reading the description is that there is a need for a set of tasks to be re-created in a new/different project (or not necessarily?) when a set of tasks is part of a repeatable process.

So, for example, when managing a marketing campaign, there could be the same set of tasks that a team always needs to get done. So instead of re-creating them every time, you would like to be able to instantly re-create them, ready in the 'todo' column.

Is that correct? If not, what are the differences? Could folks describe the usecases for which they would need something like this?

Thanks!

Liron

Group Product Manager, Jira 

the updates is - NO Update. Its on RIBS-Long

Is there a update available?

 have never seen 1500 votes on a issue which has not been implemented yet. I would say it is about time....

Even Deep Clone is good it does not cover all clone needs. e.g. elements created by the XRAY plugin are not fully cloned.

This will NEVER be included as an out of box solution because Atlassian does not want to anger or alienate premium plugin authors who make tons of money offering this as a paid plugin.

This is 100% right. The reason companies build platforms and ecosystems is so that they don't have to take on building every last bit of functionality. Should they have built this functionality into the base product? Sure. Will they? Probably not for the reason stated above, coupled with the fact that Atlassian gets a piece of every Marketplace sale, just like Apple and Google do for app sales and in-app purchases in their app stores.

Why bother putting resources on things that to most people seem like fundamental functionality when they can focus on building "high value" features like Atlassian Intelligence? They can let the ecosystem fill the gaps on "low value" features and turn that directly into revenue without lifting a finger.

Welcome to software economics in the 21st century. ¯_(ツ)_/¯

FWIW, we've found Deep Clone to be excellent for this.

We have been using the importer tool as a workaround to not being able to bulk-clone tickets–it's not ideal and has its own limitations, but does allow us to generate most tickets needed for specific project-types in a release.

Now, Jira Cloud is stating that the importer tool is going to be restricted to Site and Org admins (starting in April; full roll out by end of June 2024). This is going to eliminate the seemingly closest solution we have within my org, as most users are not Site or Org Admins.

There is an open suggestion ticket to REMOVE this new update before it is rolled out for anyone who is interested:
https://jira.atlassian.com/browse/JWMCLOUD-644

We would love to see the bulk-clone feature come to life ASAP.

With this function, the world will be a better place to live.

Any updates?

@valdamir I agree with your concerns about the likely limitations of a full data map even with bulk-clone added.  

However, let's not give Atlassian any excuses to avoid turning on the first, required, simple capability:   Very similar to bulk move, Allow customers to pick N issues and do the equivalent of hitting the "clone" button in the drop down menu.  That's all.

Let's start there and keep the request simple and clear in front of Atlassian.  There should be no excuses on this simple request.  Let the add-in folks make their money on the more complex mapping and field resetting options.  

At this point, it's pretty much safe to say, that Atlassian is full of ****. You pretty much get forced to their cloud with the deprecation of the server version (and the atrocious license model that data center is), and yet the cloud is missing essential features that our teams (and obviously many other teams as well) can't live without. Medium-term, we will abandon Atlassian products and move away from this arrogant company. We already started to reduce our general dependency on their products.

" added a comment - Yesterday
This will NEVER be included as an out of box solution because Atlassian does not want to anger or alienate premium plugin authors who make tons of money offering this as a paid plugin."

Yet simultanously, Atlassian buys out competing plug-ins that have also HAD THIS cloning functionality, but mysteriously afterwards Atlassian have shut them down and never incorporated this functionality into their own products. 

Unfortunately, even with that paid plugins it's not possible to get full (bulk) clone functionality. When additional plugins such as Xray are used data are spread in plugin vendors' clouds and it's impossible to get full "data map" to clone them fully.

I do not understand why Jira Cloud is designed in such strange way and it will bring only troubles and headaches one day...

This will NEVER be included as an out of box solution because Atlassian does not want to anger or alienate premium plugin authors who make tons of money offering this as a paid plugin.

This was entered 10 YEARS ago. Why has this not been addressed at this point? Because they literally dont give a fuck.

This is maddening.  Emily Ditchfield should explain a bit more to customers about why this capability is not provided.  Simply saying "many factors" is not sufficient.  Please comment on

1) Has the interest not met some threshold?

2) Is there something about the implementation that violates some other constraints?

3) Are the revenue generating/sharing relationships with bulk-clone add-in providers in the way?

The lack of an ability to easily clone-move all my deferred issues to the next project is crazy.  I find myself googling/GPT'ing over and over thinking that I must be missing something.

BTW, this is +1 up-vote if you can't tell

+1 this would save LOTS of time, but i assume you already know that.  In Cloud does cloning and Epic clone is linked stories?  We have server for now (upgrading soon)

Yes please! Many Product Managers would appreciate this feature as a time saver. 

I had 3 kids, 3 K.I.D.S, since this ticket was submitted.

Bulk Move is already there why not Bulk Clone/Copy? It is basic feature.

Pretty Please would love this, thank you! 

Why customers should pay for this feature through extra plugin in? Revenue...? Even e.g. Deep Clone plugin is really good it does not cover all possibilities - mainly when other issue types are added by another external plugin e.g. Xray.

The architecture when data are served and stored out of Jira already brings and will bring even more troubles in the future. Already now it's obvious slowness when these plugins are loading visual elements and data.

+ 5 from our entire PM team

We're a consulting company that has projects that are very similar and our processes require the same steps in order to effectively scope and execute a project. We already are planning to spend money on Add Ons, which we are happy to do as this feature seems to be overlooked as a necessity. This is the type of thing that splits our PM team and makes them want to leave JIRA. Please add this feature.

+1

Will this basic function in plan or still on hold?

+1

+1

When are you planning to do such a useful and basic functionality?

Bulk clone is standard on other testing tools and ridiculous that Atlassian cannot be bothered to sort out.

Would rather point you to add ons that are chargeable where I am sure they take money for recommending.

They concentrate on messing permissions and other features that are not useful at all

Follow +1

For us, this features determines whether we move to the cloud or stay on-prem (or abandon Jira in general, which is likely).

Ridiculous

Atlassian has been gathering interest for almost a decade on this, or more likely they are just letting 3rd party developers create the functionality for them and dipping into that sale without having to do anything. 

Atlassian is really dropping the ball on this matter. This is an enhancement that is truly needed. This functionality is included on the server version however, Atlassian is deciding to discontinue the server version This is not available in cloud version? How does that make sense? Atlassian should be ashamed of themselves as a company.

@Emily Ditchfield why would this be tracked for 9 years. It is clear there is an overwhelming need. How long can you gather Interest and what does it mean there is a need for more unique votes?

I don't normally comment on here - and I also do not necessarily pick this feature as my mountain to die on (there would be others ) - but it would be great if we could get some feedback / visibility into things like which feature this one might be competing against, challenges that adding this feature would / could present in implementation, etc.

I certainly understand and have appreciation for the difficulties that a product development roadmap presents and as such it would just be really good to have better visibility into where / how things are ranked in terms of priority and what is driving that. 

Having said that, it would certainly be a fine line between providing that visibility and opening oneself up to the vitriol that the soap box that is the internet presents, so I'll leave the request here and leave it to your judgement. Thank you.

Hi Emily,

This issue is FAR beyond the "gathering interest" stage, don't you think? As a project manager myself, I understand the impact to scope that adding an additional feature that was not planned for a given period can have. However, I also understand that the volume of user feedback for a particular feature is an important driver in determining what a PM decides to either add to scope or ignore (maybe plan for later). This issue has been going on for a substantial time now and so many users have requested it, that I would think you would prioritize it into your scope for implementation, otherwise you are not listening to your users and your "gathering interest" statement would be seen as disingenuous. It would be far better, IMO, to just say we have decided not to implement this feature, so that people could move on and forget about it, rather than continuing to hope it is ever going to get added.

Thanks everyone who left comments and reached out to me to give me more detail here. We really appreciate the time taken, it's been very informative. 

For now this capability is still in gathering interest, we will keep you posted on this JAC ticket on any updates to our plans for this functionality.

Cheers,

Emily Ditchfield

Product Manager, Jira Software

Bulk cloning is a needed functionality as soon as possible. Cloning on an issue by issue basis is time consuming and not efficient process at all. 

if you don't allow for template issues at least let us clone all children in a ticket...

Similar to the previous few comments:

We would like to set up a skeleton "project" in Jira which contains a significant amount of base content (Epics, stories, subtasks, attachments). Every time we have a new Customer/Project, we would like to create a copy of the skeleton "project" which can then be adapted/modified for the specific customer company.

Currently, we are doing it with export/bulk import but it's less than ideal.

I can +1 the previous comments and use cases, especially the one mentioned by Anna: cloning Epics and the tasks under them. Currently there is no way to do this natively in Jira.

We use these for various reasons, including in projects when for example a certain work package or additional work is ordered for a project. In these cases we just need to copy a suitable Epic and its tasks, whereas using a project template creator (like Delegated Project Creator for Jira) or blueprints is too overkill and not suitable to cloning just a handful of issues.

Similar to Baptiste's comment, we have sets of steps that we repeat for onboarding new team members/partners that may need to be assigned to different teams to implement, as well as a set of tasks that happens each time we launch a new website, etc. So our ideal structure is a template ticket that has 20+ subtask tickets underneath it that we want to clone each time (so that each subtask ticket can be assigned to the right person.)

As of now, we've had to create a single ticket we can clone with a checklist of the 20+ items inside it, but that can only be assigned to one person, so creates a lot of extra work in tracking and communicating, which could be avoided with the ability to clone a whole set of tickets (tasks and subtasks.)

Another similar need would be to clone an Epic with all its tasks underneath it all at once (though for our particular needs the task with subtasks makes more sense.)

Hope that helps!

Emily, our use case is very similar to the previous comments. We have set, repeatable tasks that should be followed for each of our teams "services" that get used over and over again. Being able to clone as opposed to uploading a CSV file would be a big improvement, as users get to stay within Jira instead of leaving Jira to put together an excel file for upload. It would be a lot more intuitive for users to clone, they go there now anyways. 

Emily,

Our use case : we do out of the box deployments of applications, we have a set of projects we call templates and for each new deployment we bulk duplicate our template into a new deployment project with all the associated info (original estimates, predecessor/successor links, descriptions, etc..)

Currently we use a plug in (Deep Clone) which does the job (except for checklists) but this would be great to have it within Jira and not to have to pay for such a basic functionality.

Cheers

Emily, very basic use case: Having a project we consider as a template, with a lot of cards with pre-filled text checklists etc, that we would like to clone/copy

2 examples:

• Employees onboardings. Each Jira issue is a task, with instructions, sub-tasks, objectives, etc. Having a template that we can clone for each new hire would be helpful, instead of creating each project and issue one by one
• Sales leads management. One project per prospect, all cloned from a template.

++++1

We need this feature.

+300 users from here... why is such a basic functionality still absent from Cloud? It was present in Server until Atlassian bought the add-on provider and shut them down... still haven't seen the same features implemented into Cloud.

+100

+1. Before tickets need to move on another project which linked to automated cases (test using xray), it would be great to have cloning issues at a time

+1

This would be extremely useful, especially with using tests through Xray. Cloning one issue at a time is very time consuming.

I use fixVersions and Epics with my sprint planning.  I have many repeatable stories that are attached to different Epics.  Cloning each story one at at time is so time consuming and frustrating.  Please make changes to allow multiple story cloning.

+1

+1

+1
so hard to use, when duplicate case need reuse

+1

+1

+1 Please add

+1 - Need to copy a bunch of Windows release related testing tasks and it would be nice to bulk clone all of the tasks we did last year for the various products. 

+1

+1

+1

+1

+1

Hello, is this thing on? This has been "gathering interest" since 2014. Is this a typical timeline for projects??

++1

+ 1 - Why isn't this part of the bulk operations menu? And PLEASE allow to unlink the two issues. 
Also would be great to include sub-tasks etc.

+1

+1

+1

+10000

+100

+1

+1

+1

+1

+1

Me too!

+1

+1

+1

+1

+1

+1

+1

+1

+1

+3 (at our company!)

+1

+1

+1

+1, really, really need that happening! 

+1

Our teams sometimes have the need to bulk clone multiple issues between projects, so as to not have to clone them individually or upload them from CSV. Please enable the bulk change - Clone option so we can effectively clone multiple issues at once.

+1