# Drag & Drop child entity to another parent

**URL:** <https://community.fibery.io/t/drag-drop-child-entity-to-another-parent/2580>\
**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:** 1\
**Showing post:** 6

<div class="post-metadata">

**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")

</div>

> [@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.

---

_[View the full topic](https://community.fibery.io/t/drag-drop-child-entity-to-another-parent/2580)._