# \[DONE\] Duplicating Tasks - doesn't duplicate child subtasks

**URL:** <https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322>\
**Category:** Misc\
**Created:** [October 22, 2023, 4:37am UTC](https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322 "2023-10-22T04:37:07Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![IMTanuki](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/imtanuki/32/7751_2.png) [@IMTanuki](https://community.fibery.io/u/IMTanuki)\
**Post date:** [October 22, 2023, 4:37am UTC](https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322/1 "2023-10-22T04:37:07Z")

</div>

I have a project -task - subtask hierarchy  
I have a task template that includes a sub task template

When I duplicate the task template, I’d the duplication to similarly duplicate the usbtask, but this isn’t happening.

I have a 1:M relationship established between the task - subtaks databases.

Is there a simple way to handle this?

Thx!

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 22, 2023, 2:05pm UTC](https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322/2 "2023-10-22T14:05:16Z")

</div>

There is no ‘simple’ way to achieve this, but you might want to look at the [Templating example](https://fibery.io/templates/templating) to see if it can inspire you on how you could do it with automations.

---

<div class="post-metadata">

**Author:** ![IMTanuki](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/imtanuki/32/7751_2.png) [@IMTanuki](https://community.fibery.io/u/IMTanuki)\
**Post date:** [October 22, 2023, 11:12pm UTC](https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322/3 "2023-10-22T23:12:01Z")

</div>

Chris - thx so much for the quick reply. I somehow suspected this would be the answer.

I looked at the automation and I recall looking at this before - I forget the issue, but I remember it had a limitation that prevented me from using it.

As a feature request, it would be great to have a deeply nested duplication function, where every child object is duplicated along with the parent. I know that gets tricky, because of the many ways child elements can be linked to a parent.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 23, 2023, 6:22am UTC](https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322/4 "2023-10-23T06:22:06Z")

</div>

> [@IMTanuki](#):
>
> As a feature request, it would be great to have a deeply nested duplication function, where every child object is duplicated along with the parent. I know that gets tricky, because of the many ways child elements can be linked to a parent.

And in workspaces that are highly-connected, duplicating an entity AND all its linked entities AND all their linked entities, etc. could result in a cloning of a large subset of the content of the workspace.

There are definitely some concrete use cases, but solving them intelligently without causing more problems is not as easy as it first appears.

---

<div class="post-metadata">

**Author:** ![IMTanuki](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/imtanuki/32/7751_2.png) [@IMTanuki](https://community.fibery.io/u/IMTanuki)\
**Post date:** [October 23, 2023, 11:16pm UTC](https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322/5 "2023-10-23T23:16:15Z")

</div>

that’s why i said, it could be tricky…🙂

I think allowing duplicating nested structures without limitation is going to far. But what is too far? In my case, I just want to copy an “empty” task and its “empty” sub-tasks.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 24, 2023, 9:45am UTC](https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322/6 "2023-10-24T09:45:10Z")

</div>

It’s probably easiest to do with a pair of automations

---

<div class="post-metadata">

**Author:** ![IMTanuki](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/imtanuki/32/7751_2.png) [@IMTanuki](https://community.fibery.io/u/IMTanuki)\
**Post date:** [April 10, 2024, 10:21pm UTC](https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322/7 "2024-04-10T22:21:51Z")

</div>

Rather than open a new post, I’d like to revisit my original request.

More and more, I’m running into situations where I need a quick and dirty copy of an entity and its children / grandchildren. Typically, this is a variation of a project in a space, where I want a second (third etc) instance of that project in the same space.

Notwithstanding the complexities of implementing a copy function, given the unlimited extensibility of Fibery’s data model, can I ask if any further thought has been given to supporting something like this?

For my use cases, implementing automation for every possible project template is overkill.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [April 16, 2026, 1:23pm UTC](https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322/8 "2026-04-16T13:23:29Z")

</div>

Now it does

> [@April 16, 2026 / gorilla Automatically link entities with more operators, Text color in rich text, Filter and sort relation selectors in Forms, Share with all users with a particular email domain](https://community.fibery.io/t/april-16-2026-automatically-link-entities-with-more-operators-text-color-in-rich-text-filter-and-sort-relation-selectors-in-forms-share-with-all-users-with-a-particular-email-domain/10744):
>
> A bulky release today with some quality of life improvements and… zero AI features (not sure whether it is good or bad though smiling_face_with_tear). Automatically link entities with more operators Before, you could use only = when describing Automatic Link Rule for a Relation Field. We extended the list of allowed operators. Now you also have: For Relation Fields: to-one relation is in to-many relation For Text Fields: starts with, ends with, contains For Date Fields: date field is within …

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [April 16, 2026, 4:09pm UTC](https://community.fibery.io/t/done-duplicating-tasks-doesnt-duplicate-child-subtasks/5322/9 "2026-04-16T16:09:53Z")

</div>


