# Can Tasks be Dragged/Sent Between Databases and Spaces? **URL:** \ **Category:** Get Help\ **Created:** [June 1, 2024, 12:40am UTC](https://community.fibery.io/t/can-tasks-be-dragged-sent-between-databases-and-spaces/6254 "2024-06-01T00:40:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Foxsay](https://avatars.discourse-cdn.com/v4/letter/f/ce7236/32.png) [@Foxsay](https://community.fibery.io/u/Foxsay)\ **Post date:** [June 1, 2024, 12:40am UTC](https://community.fibery.io/t/can-tasks-be-dragged-sent-between-databases-and-spaces/6254/1 "2024-06-01T00:40:58Z")
I’m drafting a schema to handle general tasks, long-term, intermittent projects, and knowledge/ideas. I thought I might make some sort of structure like shown, with subtasks made via a self-referencing a relation field. I can drag & drop tasks/subtasks between items in the list view (using recursive organization grouping), but how would you move a task to another database or space? ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2cbb24c0dddcdb6d819dfadf5a9b0563df5c53a4.png) ---
**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:** [June 1, 2024, 11:20am UTC](https://community.fibery.io/t/can-tasks-be-dragged-sent-between-databases-and-spaces/6254/2 "2024-06-01T11:20:14Z")
It is unclear what databases you want to have so far. For example, you have two projects, are these projects will contain same Task database? ---
**Author:** ![Foxsay](https://avatars.discourse-cdn.com/v4/letter/f/ce7236/32.png) [@Foxsay](https://community.fibery.io/u/Foxsay)\ **Post date:** [June 1, 2024, 6:12pm UTC](https://community.fibery.io/t/can-tasks-be-dragged-sent-between-databases-and-spaces/6254/3 "2024-06-01T18:12:07Z")
I’m not sure the best way to set it up, and I’m still very new to using Fibery. I was thinking separate task databases, and projects large enough could get it’s own database or space, but I’m not sure if that’s feasible. ---
**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:** [June 1, 2024, 7:29pm UTC](https://community.fibery.io/t/can-tasks-be-dragged-sent-between-databases-and-spaces/6254/4 "2024-06-01T19:29:36Z")
I’d suggest a Project database, linked (1:m) to a Task database, and then add a Category select field to your Project db to distinguish between Education and Construction projects, say. Project db can have a 1:m self-relation (so that X House Layout/Design project can be parent to Dining Room, Kitchen, Living Room sub-projects (all in the Construction category). And you can have a 1:m self-relation for the Task db so that Tasks can have Sub-tasks and Sub-sub-tasks etc. Meanwhile, you can have two Projects on the Education category: ‘IT applications’ and ‘Applied stats’. ---
**Author:** ![Foxsay](https://avatars.discourse-cdn.com/v4/letter/f/ce7236/32.png) [@Foxsay](https://community.fibery.io/u/Foxsay)\ **Post date:** [June 1, 2024, 10:00pm UTC](https://community.fibery.io/t/can-tasks-be-dragged-sent-between-databases-and-spaces/6254/5 "2024-06-01T22:00:44Z")
I like this, I could also use a tags DB or second category if it gets large enough. The only potential issue I see on its face is the number of fields getting unwieldy since different projects will likely need different fields. I believe some of the Fibery documentation warns about performance issues doing that. This is only tangentially related, but is it possible to display single or multi-select fields or something similar as buttons or checkboxes vs. drop-downs? My process sorts through a few different options/categorizations for tasks, filtering them from the view when all the required fields are filled. The best way to do this quickly that I’ve found so far is to use a bunch of checkboxes along with a kanban-view. Other types of fields would serve the purposes better, but since multi-select requires more clicks and scrolling it’s much slower when sorting a lot items.