# Drag & Drop child entity to another parent **URL:** \ **Category:** Ideas & Features\ **Created:** [February 21, 2022, 10:19am UTC](https://community.fibery.io/t/drag-drop-child-entity-to-another-parent/2580 "2022-02-21T10:19:46Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Haslien](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/haslien/32/493_2.png) [@Haslien](https://community.fibery.io/u/Haslien)\ **Post date:** [February 21, 2022, 10:19am UTC](https://community.fibery.io/t/drag-drop-child-entity-to-another-parent/2580/1 "2022-02-21T10:19:46Z")
With the multi-panel navigation it would feel easier than ever to move a child entity to another parent if you have both parents open, when the child is many to one parent. Similar, but not identical to, this one: > [@Drag Entity to Sidebar to Associate](https://community.fibery.io/t/drag-entity-to-sidebar-to-associate/561): > > Hey there – one thing I do all the time is quickly create entities (Tasks) without much detail in them, then sort them / enrich them later. A big part of this associating these tasks with other entity types (in this case, Categories). Right now this is a slow process. I can do it by clicking into the entity detail view, or I’ve created a filtered view with my Categories as the rows, then drag my tasks down to the right row… but having to scroll vertically back and forth makes this fairly painfu… **Example usage:** I have two parents of the same type open, they are both orders for a customer, and the children are ordered items. Customer decides to pay for some items later, so we just move those entities into a new order. Why is this easier? Because we don’t have to do one of the following: - go into each order-item and change parent order to the new one - go into new parent order and select existing order-item Both of those options involves either having to remember or compare the entity name to make sure you are moving to the correct one. An example: [https://i.thevirt.us/02/G9E2f.mp4](https://i.thevirt.us/02/G9E2f.mp4) **Why can’t I just use copy-paste (from referenced post above) or Kanban?** Because we have hundreds of orders, and our native way of working with these aren’t looking at a list of all items and manage them that way. We work with one Order/Order items by searching for it and opening. We’d also have hundreds of orders/order items unrelated to the one we’re working with in close proximity, which is confusing and error prone. ---
**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\ **Post date:** [February 21, 2022, 3:31pm UTC](https://community.fibery.io/t/drag-drop-child-entity-to-another-parent/2580/2 "2022-02-21T15:31:28Z")
Although not exactly the same, I was thinking along the same line but hoping for a way to copy and paste (or better yet drag and drop) an entire collection from one entity to another in this request: > [@Copy Collection/References](https://community.fibery.io/t/copy-collection-references/2523): > > I wanted to propose a copy collection items feature that would allow users to just copy all linked references in a collection and add it to another collection of the same type. For example, it would be possible to copy a list of attendees from one meeting entity and that same list to another entity. I know you are able to duplicate entities, but I think this need sometimes comes up after the entity has been created. While this is UI function (through a button or keyboard shortcut), I also wonde… ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [February 21, 2022, 10:10pm UTC](https://community.fibery.io/t/drag-drop-child-entity-to-another-parent/2580/3 "2022-02-21T22:10:47Z")
This is an interesting idea. Makes me wonder about drag-and-drop support more broadly, now that you can view multiple Entities simultaneously with relative ease. A good example would be with the upcoming Blocks system - drag a block from one Entity Rich Text to another. Maybe by default it creates a Transclude or Link, but could hold a modifier key to Move. Just thinking out loud a bit… ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [March 7, 2022, 7:31pm UTC](https://community.fibery.io/t/drag-drop-child-entity-to-another-parent/2580/4 "2022-03-07T19:31:15Z")
Drag’n’dropping cards between panels is a very tempting idea indeed. We’ll likely experiment with it in the upcoming months — the only potential showstopper is technical infeasibility 😅 ---
**Author:** ![Dominic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dominic/32/5348_2.png) [@Dominic](https://community.fibery.io/u/Dominic)\ **Post date:** [July 14, 2022, 4:06pm UTC](https://community.fibery.io/t/drag-drop-child-entity-to-another-parent/2580/5 "2022-07-14T16:06:47Z")
I feel this is one of the main reasons people are having trouble adapting to the “new” panel navigation paradigm. It seems so intuitive that you would be able to do this that and it’s very frustrating when you realize then panels can’t communicate with one another. Adding this would dramatically speed up many common interactions for us. ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [January 3, 2024, 10:45pm UTC](https://community.fibery.io/t/drag-drop-child-entity-to-another-parent/2580/6 "2024-01-03T22:45:04Z")
> [@antoniokov](#): > > Drag’n’dropping cards between panels is a very tempting idea indeed. We’ll likely experiment with it in the upcoming months — the only potential showstopper is technical infeasibility 😅 Did you ever end up experimenting with this @antoniokov? To me, this feature (alongside [grouping in lists/tables by any field](https://community.fibery.io/t/planned-row-grouping-and-total-row-in-table-view/532) and [self-relations-on-bottom-levels](https://the.fibery.io/@public/Public_Roadmap/Roadmap_Item/Add-self-relations-on-bottom-levels-244) are hugely impactful usability features that your primary competition already have and would likely contribute to higher adoption/lower churn if they were addressed. I know the other 2 features I mentioned are in the calendar for Q1 2024 so hopefully drag & drop improvements could be prioritized soon after. ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [January 4, 2024, 3:31pm UTC](https://community.fibery.io/t/drag-drop-child-entity-to-another-parent/2580/7 "2024-01-04T15:31:25Z")
Not really, unfortunately: we switched to other things. A second chance might come when we redesign the Timeline/Calendar backlog which is clearly a joke now 🙈 P.S. Could you please share which primary competition has drag’n’drop between panels? Perhaps, we can draw some inspiration.