github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Feature Request: Move Task with Destination Bucket Selection #2541

New Issue
Open
opened 2026-03-22 14:11:30 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-22 14:11:30 -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 when moving a card in Vikunja, it is moved to the default bucket within the target project/board. There is no option to select the specific destination bucket during the move process. This creates unnecessary extra steps, as users must move the task and then manually relocate it again to the correct bucket.

Proposed Solution:
Enhance the move functionality to allow users to choose the destination bucket when moving a task.

Move Task
• Option in task menu: Move
• Allow user to:
• Choose destination project/board
• Choose the destination bucket within that project
• Optionally choose position in bucket (top, bottom, or specific order)

Default behaviour:
• If no bucket is selected, use the current behaviour (default bucket).

Here is an example video of how it can be done in Trello:
https://github.com/user-attachments/assets/67327c69-1c28-4c4c-aa0f-c08bc264941f

Benefits
• Reduces friction when reorganising tasks
• Improves workflow across multiple lists within a project
• Eliminates unnecessary intermediate steps

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 when moving a card in Vikunja, it is moved to the default bucket within the target project/board. There is no option to select the specific destination bucket during the move process. This creates unnecessary extra steps, as users must move the task and then manually relocate it again to the correct bucket. **Proposed Solution:** Enhance the move functionality to allow users to choose the destination bucket when moving a task. Move Task • Option in task menu: Move • Allow user to: • Choose destination project/board • Choose the destination bucket within that project • Optionally choose position in bucket (top, bottom, or specific order) Default behaviour: • If no bucket is selected, use the current behaviour (default bucket). Here is an example video of how it can be done in Trello: https://github.com/user-attachments/assets/67327c69-1c28-4c4c-aa0f-c08bc264941f Benefits • Reduces friction when reorganising tasks • Improves workflow across multiple lists within a project • Eliminates unnecessary intermediate steps ### 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#2541
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?