github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-07-15 14:22:28 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Feature Request: Move Bucket Between Projects/Boards #2542

New Issue
Open
opened 2026-03-22 14:11:31 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-22 14:11:31 -05:00
Owner
Copy Link

Originally created by @sunilnc on GitHub (Feb 16, 2026).

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same feature request.

Description

Problem:
Currently in Vikunja, buckets are tied to their original project/board and cannot be moved directly to another project. Users must recreate buckets manually or move tasks individually, which is time-consuming and inefficient when reorganising projects or restructuring workflows.

Proposed Solution:
Add the ability to move a bucket from one project/board to another.

Move Bucket
• Option in bucket context menu: Move
• Allow user to:
• Choose destination project/board
• Choose position within the destination project (optional; default = end)
• Preserve tasks, ordering, and metadata

Default behaviour:
• Bucket retains all tasks and associated metadata (labels, attachments, comments, assignees, subtasks).

See an example of how it is done in Trello:
https://github.com/user-attachments/assets/8e0dccd3-82ac-415a-972a-d1f855421506

Benefits:
• Enables easier project reorganisation
• Supports evolving workflows and restructuring
• Avoids manual recreation of buckets and tasks

Which alternatives did you consider using instead?

See above

Originally created by @sunilnc on GitHub (Feb 16, 2026). ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same feature request. ### Description **Problem:** Currently in Vikunja, buckets are tied to their original project/board and cannot be moved directly to another project. Users must recreate buckets manually or move tasks individually, which is time-consuming and inefficient when reorganising projects or restructuring workflows. **Proposed Solution:** Add the ability to move a bucket from one project/board to another. Move Bucket • Option in bucket context menu: Move • Allow user to: • Choose destination project/board • Choose position within the destination project (optional; default = end) • Preserve tasks, ordering, and metadata Default behaviour: • Bucket retains all tasks and associated metadata (labels, attachments, comments, assignees, subtasks). See an example of how it is done in Trello: https://github.com/user-attachments/assets/8e0dccd3-82ac-415a-972a-d1f855421506 **Benefits:** • Enables easier project reorganisation • Supports evolving workflows and restructuring • Avoids manual recreation of buckets and tasks ### Which alternatives did you consider using instead? See above
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2542
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?