I think it's pretty safe to say there is no chance this will ever be implemented.  Opened in 2013, it is now more than 8 years old.   Still no official response from Atlassian except "no more information at this time" 5 years ago. Too bad.  I guess we should probably go to another provider of issue tracking software.  Bugzilla anyone?   

+1

+1

This is pending from 2013. Am wondering why is this not being picked up, despite several users voting for it.. Its a pain to manually clone tons of stories... We have to support several versions.. And needs to clone stories for every version.
Absence of this functionality is causing time wastage and productivity loss

+1

+1

I would like to have this too. 

Issue was created in 2013, it's a key/fundamental requirement! It's been almost 8 years now and such a key FR is still being being considered to be placed on the roadmap. What a shame!

I would very much like this feature.  Can we get this on the immediate roadmap?!

I was able to clone an epic with all stories. There is a new option `Clone Epic` and it helped. I am using Jira service desk (cloud) and this is a software project.

As I commented already before, there are apps on the marketplace doing exactly what you are looking for.

See this as an example: https://marketplace.atlassian.com/apps/1222030/epic-clone?hosting=server&tab=overview

Especially with the latest announcement by Atlassian to end support for Server and to focus on Cloud I think there won't be much development efforts to implement such features. Therefore, I would recommend to look for an app which is providing this features. Even if those apps are not free and require some investment, you should consider how much time they will save your users who can clone an Epic together with all issues in Epic at once instead of doing all that manually.

I don't think there are technical blocking points or challenges for Atlassian to implement this. They just have the focus on other things at the moment.

I started watching this issues years ago and it's still very important to us. Is there a fundamental technological challenge?  We either need a template feature or a way to clone epics as our epics x tasks are repeated over and over and I can't get my users to adopt Jira because it's too time consuming for them to manually create all of the issues under each epic. 

Cloning the epic and then manually linking each story is too time consuming. This would be a nice feature to have on Jira server instead of cloud only. 

Why is this feature taking so long to add?  It is obviously something that the user base would like to see as an added feature.  Please expedite this request.

can't believe that such an elementary feature does not exist

I wouldn't wait for Atlassian to implement this as they wrote above in the status that their priorities are somewhere else. Although this comment is from 2018, I don't think that something changed here.

As Bridy wrote before, there are apps on the marketplace doing this. Beside Clone Plus you could also use

Duplicate Epic (Server, free): https://marketplace.atlassian.com/apps/1220519/duplicate-epic?hosting=server&tab=overview

Epic Clone (Server + DC, paid): https://marketplace.atlassian.com/apps/1222030/epic-clone?hosting=server&tab=overview

The Clone Plus app from Bob Swift recently added this functionality - we've been really happy with it!  https://marketplace.atlassian.com/apps/44043/clone-plus-for-jira?hosting=cloud&tab=overview 

Please add this feature, people have been requesting it since 2017

Please add this feature ASAP

I need this so much. One of my EPIC has 89 Tasks under it, and now its required to be clone for another version. 

We could also use this feature a lot

also for our Elsevier users this would be a benefical addtion, I am very surprised this mostly likely very simple addition is not part of the product

Any update on this feature? It would be extremely beneficial to do this. We just had a customer have to go through a much longer process to clone 28 issues into a new subtask. If cloning allows you to clone the Sub-tasks, why can't we do it with Epics? 

Can you please provide an update on where this is on your roadmap and possible target release date? 

Hi team,

we need this feature as well. Should be a basic function from Jira.

This ticket was 7 years ago created, a lot of votes and no results.

This is a pity

Kind regards

Marcus

I need this as well.

I'm very surprised that this topic was not prioritized higher. It would definitely help in multiple projects. I hope we will get more votes on that soon.

Need this feature, as its going to be very helpful for creating similar kind of Tasks, which have sub-tasks under it.

We are using the https://marketplace.atlassian.com/apps/1220519/epic-clone (free plugin), and it´s working great for our need.

I also need this function.

Also keen to see this.

Any updates on this matter?

Please, please, please add this feature. So helpful for those of us who aren't allowed to add plugins. 

This would be really, really great to have. Could save us bucoo time.

I feel like I'm having the Berenstain bears/Mandela effect.  I was able to clone epics and all related tasks would clone too.. as of just a few days ago.  But now it will not work.  

The Matrix has been changed!  Hah

@Raison D'Souza, as a workaround we use the External System Import feature and have a CSV template for the repeating pieces. Hope that helps. 

This would be super useful for templatizing repeated pieces of work. Surprised that is not already supported.

Any workarounds in the meantime?

Hey,

we just released an app which adds the functionality to clone an epic with all issues in epic:

https://marketplace.atlassian.com/apps/1220519/epic-clone

Maybe you can give it a try as long as there isn't any progress from Atlassian on this - it's free

I would appreciate your feedback on this app.

This enhancement would save our company hundreds of hours per year. Please prioritize this enhancement.

Are there any further updates on the initial request to copy linked stories when cloning epics?

I'm standardizing project management/execution tracking across the company using Jira/Confluence.  For repetitive work, many users are asking for ability to clone epic with its child stories;  It would be great help with improving efficiency of project admins (or anyone else generating backlog).

+1

+1 

+1

+1

+1

+1

Vote Yes!

+1

+1

+1

This has become a critically needed feature for many teams in our space. 

Critical feature for me as well. 

This would be very helpful. Currently using xls for external import of multiple stories in an epic. Please and thank you!

I eagerly am staring at "Fix Version/s" to see if 8.0.0 appears with a refresh. Pretty please.

Agree, critical feature for us as well.

Chiming in here again. This is a very important feature to us. 

This would be an extremely useful feature.

We have a whole bunch of Epics which are very similar in structure. It is taking quite some time to clone them.

Also the Template (Epic) cloner for Jira does not work for cloud instances.

Please can this be platelisted for development and incorporated into the Jira software?  It is something GREATLY needed.  

WHY isn't this a basic feature!? BC someone gets money from an addon. This is seemingly a core tactic in their revenue strategy.

Checkout taiga.io for an amazing alternative.

Why is this still unassigned?

Please move this ticket up in your backlog. It could save me and my team hours of countless taskmastery

Move this to the top of the backlog please.  

It makes sense from a feature symmetry perspective that if you can clone one hierarchy , you should be able to clone another one 

Hi,

as there won't be any progress on that feature request in the nearest future, a workaround might be interesting. As I was facing the same problem I implemented a solution with scriptrunner. I posted the code here:

https://community.atlassian.com/t5/Marketplace-Apps-questions/Bulk-Clone-Pro-How-to-clone-entire-Epic-with-Issues-and-their/qaq-p/626470#M46442

Maybe that will help some of you.

Push!

Hi - does this mean someone is actively looking at this issue? It still shows as unassigned...

badly in need of this Feature. Please provide it ASAP

There is a plugin called "Template (Epic) cloner for Jira". It does what has to be done for a low price.

Altlassian could buy this and include in the standard. Very easy, or?

Maybe, instead of this Jira project, we all create incidents in order to grab someone's attention. 

+1 on this!

I really need this feature

This feature is kind of a baseline requirement for creating modular projects

Our team has a need to clone Project Management tasks that will apply to all our projects. We would like to create an epic called "Project Management" in each of our projects that tracks higher level PM tasks such sending thank you cards/client gift, adding the project to our portfolio, prepare launch plan, retrospective, etc. These tasks are pretty much the same on most of our projects and we need a way to clone this PM epic with all the PM related tasks (that have nothing to do with feature development) from project to project.

I'm now having to painfully clone several dozen user stories individually and manually link to a new epic. Why can't this be done at once? There are tons of useless new features, but not this very common thing?

this feature would save us time

this would be a beneficial addition, as it sucks cloning dozens of tasks assigned to one parent epic for multiple projects

This functionality would be extremely beneficial to me.  We find ourselves doing the same set of tasks over and over again for each client as we bring them on board to our platform, and having to re-do the list of tasks every time is not enjoyable.

This feature would be immensely useful for what I do. I work in a Scaled Agile environment whereby we have up to 3 levels of Tiered Epic's. We have 7 level 1 (Portfolio level) Epic's that contain a broad set of requirements, sometimes up to 50 stories per Epic, x7 Epic's. 

Those Epic's are cloned into a level 2 epic (Program level) to give them the context of an implementation team. If the context is again subdivided into larger specialized implementation teams, like say a huge application with 10 dev teams working 10 different feature sets, we clone the Level 1's into a level 3 (Dev Team level) to give it again a more focused context.

Then we have stories and sub-tasks to the stories, some stories have 4 or 5 sub-tasks.

By the end of the year I'll have 35 implementation teams to track in our portfolio all have the same requirements from the 7 Level 1 Epic's. I need to clone them and the ~300 stories and ~500 sub-tasks each, 35 times.

Doing that by hand sucks.  

Please build this feature so I don't have to clone ten thousand stories this year by hand  I will send you cookies! COOKIES FOR ALL OF OUR DEVS!

What's worse Joseph, is that there is a Bot that runs to move things to a various states based various aspects of activity.  I don't work for Atlassian, but I've seen the evidence of it in the activity logs on the tickets.

I think Atlassian could benefit by being a bit more transparent on their roadmap when it comes to community contributed issues.  E.g. this is a pretty sad list of Releases sitting "unreleased"

https://jira.atlassian.com/projects/JSWSERVER?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=unreleased

And this isn't much of a roadmap for what's next:

https://jira.atlassian.com/secure/RapidBoard.jspa?projectKey=JSWSERVER&rapidView=1904

https://jira.atlassian.com/projects/JSWCLOUD/versions/70406

Everything of "medium" to "low" priority... and yet the Customers are screaming.

This report is telling though:

https://jira.atlassian.com/secure/RapidBoard.jspa?rapidView=1904&projectKey=JSWSERVER&view=reporting&chart=cumulativeFlowDiagram&swimlane=4655&swimlane=4656&swimlane=4657&column=11168&column=11169&column=11170&column=11171&column=11173

I don't want to turn this into an off-topic rant, but hopefully this provides some added encouragement.

The funny part of this ticket @victor is you can sort all open tickets by votes and see this one is up there from a customer perspective. It is actually a bit shocking that Atlassian has not at least made a note on this ticket for the last review time to alert us customer which actually care to give feedback; very poor show indeed. I suspect that is also true for most issues. 

As an architect, this forces me to consider how I can make my organization more agile - by finding a better offering...and vote with my companies wallet. 

Is any of the tickets for Atlassian every got resolved? I tried the Created vs Resolved chart, but I am not an employee.

Maybe we should send in a mail ballot instead of internet vote?

Going to chime in again though it seems pointless. I do this all the time, now I'm forced to manually recreate each story. Seems like such a no-brainer to implement. 

I agree!

I'll add another comment to the list. Been watching in my inbox for a year as well. 

I hadn't commented either, but I've voted.  I hate the comment spam, but if it's comments that get the job done...  :-/
Come on Atlassian... Just do this.

Status says that this issue needs  "more unique domain votes and comments" to be rewiewed. So Atlassian, you want me to leave a comment every other week how crucial this actually is?

I've been watching this issue for years and I'm tired of all the mails in my inbox.

Hilarious @victor

You hit the nail on the head. This item (and many more) has got hundreds (500+) of votes over 5 YEARS. What is the point of these forums when Atlassian obvious does not have any interest in their user base pain points and suggestions.

They would rather change their pricing structure and develop convoluted UI's for their systems that look pretty bust make the UX profoundly confusing. 

Its a classic "if it ain't broke, fix it", "if its broke, ignore it"

You may be able to sense my frustration.

I would like to be able to set up a standard epic with stories & subtasks for a recurring project, just once, with all the relationships/links, tags, components, descriptions, set up.

Even if I have to do this manually one time (as opposed to cloning an existing issue & removing the detritus), that would be fine.

I just don't want to have to spend 4h doing it every time we do the work for a new client.

This seems like a fairly trivial feature to implement on the backend. Please prioritize it! 

The voting seems to create an illusion that it would make any difference. We really need this feature. How many more votes do we need?

this is SUCH a pain.  Every time we start a new project I either have to export all the task from the old Epic and then import them into a new epic, or I have to keep an Excel sheet updated with our task list and import it.  Since the task list slowly changes over time, I always have to remember to modify the current Epic, and the Excel, so that when I need to start a new Epic the Excel will be current.  I know teams using Jira for software stories likely don't need this bulk clone feature, but anyone using Jira for project management surely would appreciate it.  I guess it wouldn't be so bad if the Importer were easier to use, but that is also a bit of a pain, and it seems to never be able to correctly process the Account field for Tempo, so I end up having to update that manually.

My company needs it in Jira cloud as well. This would be a huge help!

Linked tasks (and those tasks' sub-tasks)

This would be god send

My company badly needs this feature in Jira Cloud as well.

Yet another vote, there are now 496.

Atlassian, how many votes are required for you to consider this request?

Hi Atlassian. If I could include all the users in my company waiting for this feature, you would have +3,400. Is there a product manager/owner looking at this?

I will add my vote, but also expand this by including the 'clearing' of dates.  Cloning an epics with start dates in the past just causes other problems if the dates aren't cleared manually.

added my vote...

+1

Seems pointless since this has been open for 5 years with no action but a +1 from me. We close epics all the time and it's a pain to manually recreate the structure.

+1

+1