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

[GH-ISSUE #114] Bulk edit for tasks #5820

New Issue
Open
opened 2026-04-20 16:09:15 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-20 16:09:15 -05:00
Owner
Copy Link

Originally created by @svigneau on GitHub (Jan 1, 2022).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/114

It would be useful to enable bulk edit for tasks. This could be used, for instance, to reschedule multiple tasks at once.

Originally created by @svigneau on GitHub (Jan 1, 2022). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/114 It would be useful to enable bulk edit for tasks. This could be used, for instance, to reschedule multiple tasks at once.
GiteaMirror added the area/task-editorarea/task-metadata labels 2026-04-20 16:09:15 -05:00
GiteaMirror commented 2026-04-20 16:09:18 -05:00
Author
Owner
Copy Link

@dpschen commented on GitHub (Jan 3, 2022):

See: https://kolaente.dev/vikunja/frontend/issues/445

<!-- gh-comment-id:1934137177 --> @dpschen commented on GitHub (Jan 3, 2022): See: https://kolaente.dev/vikunja/frontend/issues/445
GiteaMirror commented 2026-04-20 16:09:20 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 1, 2025):

Since the issue has been moved to this repo, let me add more details here:

Original issue by W-Floyd on 2021-03-27T19:04:30.000Z

It would be great to be able to modify a number of items in the same way at the same time. For example, to be able to select several items and set the same due date (useful in my case for homework assignments).

Original issue on Gitea

@kolaente commented on 2021-03-28T14:40:52.000Z:

This is already partially implemented, at least on the api side. "Only" the frontend is missing.

xeruf commented on 2022-07-08T15:11:55.000Z:

This is a bummer, deleting all my test tasks is gonna be a real hassle now, as well as adding labels and assignees to the newly created tasks :/

xeruf commented on 2023-03-30T01:18:36.000Z:

It should be easiest to add such checkboxes to the Table view, which I find pretty useless so far.
If you could also double-click into any cell to edit the value, it would suddenly become really useful!

dpschen commented on 2023-03-30T09:59:30.000Z:

Generally: we really need multiselect. We also already have that on the roadmap.
Some feedback regarding the stuff you wrote here:

It should be easiest to add such checkboxes to the Table view, which I find pretty useless so far.

I agree that it could be more useful, but the moment we implement it we should make it build it so that it works everywhere.

If you could also double-click into any cell to edit the value, it would suddenly become really useful!

Double-click might make sense in the first moment, but the more you think about it the trickier it gets. The reason is that double click are actually two chained operations:

  1. If clicked item is unselected, mark it as selected.
  2. If a second click follows shortly after, we do the action.

That means as a conclusion that if an item is 'double-clickable' a single click must select it. Even if we ignore this usual pattern we still need to be able to distinguish between single and double click. For that we would need to wait a bit in order to check if a second click follows the first click in a certain time frame. If it doesn't we do the single click action (marking as active).

Since we currently open a new window / modal on single click, 'normal' selection wouldn't be possible.

Because of all of this I currently would prefer the following approach:

  • An edit button at the top which enables 'multiselect mode'. This pattern is very common on mobile devices.
  • Additionally: long click to mark and go in 'multiselect mode'. The latter doesn't have the best ux (not everyone is able to hold something 'long'), but it would only be an alternative method. Also it doesn't conflict that much with the current single click to open pattern.
  • Third pattern that could be added later: click and drag to create a selection rectangle (similar to Notion).

xeruf commented on 2023-09-03T18:28:32.000Z:

Since we currently open a new window / modal on single click, 'normal' selection wouldn't be possible.

Note that I am only talking about the Table View here.
We can preserve the ability to open up the task detail view by clicking on the ID (which can't be edited anyways) and simply allow editing any other property by a single click in the table cell, similar to Notion.

I don't see why we need checkboxes in all views or a multiselect mode. Sure that's a nice to have, but I think simply having a checkboxes column in table view would already be a nice step up and much easier to implement.

<!-- gh-comment-id:2769736575 --> @kolaente commented on GitHub (Apr 1, 2025): Since the issue has been moved to this repo, let me add more details here: _Original issue by W-Floyd on 2021-03-27T19:04:30.000Z_ It would be great to be able to modify a number of items in the same way at the same time. For example, to be able to select several items and set the same due date (useful in my case for homework assignments). [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1768) --- _**@kolaente** commented on 2021-03-28T14:40:52.000Z_: This is already partially implemented, at least on the api side. "Only" the frontend is missing. --- _**xeruf** commented on 2022-07-08T15:11:55.000Z_: This is a bummer, deleting all my test tasks is gonna be a real hassle now, as well as adding labels and assignees to the newly created tasks :/ --- _**xeruf** commented on 2023-03-30T01:18:36.000Z_: It should be easiest to add such checkboxes to the Table view, which I find pretty useless so far. If you could also double-click into any cell to edit the value, it would suddenly become really useful! --- _**dpschen** commented on 2023-03-30T09:59:30.000Z_: Generally: we really need multiselect. We also already have that on the roadmap. Some feedback regarding the stuff you wrote here: > It should be easiest to add such checkboxes to the Table view, which I find pretty useless so far. I agree that it could be more useful, but the moment we implement it we should make it build it so that it works everywhere. > If you could also double-click into any cell to edit the value, it would suddenly become really useful! Double-click might make sense in the first moment, but the more you think about it the trickier it gets. The reason is that double click are actually two chained operations: 1) If clicked item is unselected, mark it as selected. 2) If a second click follows shortly after, we do the action. That means as a conclusion that if an item is 'double-clickable' a single click must select it. Even if we ignore this usual pattern we still need to be able to distinguish between single and double click. For that we would need to wait a bit in order to check if a second click follows the first click in a certain time frame. If it doesn't we do the single click action (marking as active). Since we currently open a new window / modal on single click, 'normal' selection wouldn't be possible. Because of all of this I currently would prefer the following approach: - An edit button at the top which enables 'multiselect mode'. This pattern is very common on mobile devices. - Additionally: long click to mark _and_ go in 'multiselect mode'. The latter doesn't have the best ux (not everyone is able to hold something 'long'), but it would only be an alternative method. Also it doesn't conflict that much with the current single click to open pattern. - Third pattern that could be added later: click and drag to create a selection rectangle (similar to Notion). --- _**xeruf** commented on 2023-09-03T18:28:32.000Z_: > Since we currently open a new window / modal on single click, 'normal' selection wouldn't be possible. Note that I am only talking about the Table View here. We can preserve the ability to open up the task detail view by clicking on the ID (which can't be edited anyways) and simply allow editing any other property by a single click in the table cell, similar to Notion. I don't see why we need checkboxes in all views or a multiselect mode. Sure that's a nice to have, but I think simply having a checkboxes column in table view would already be a nice step up and much easier to implement.
GiteaMirror commented 2026-04-20 16:09:21 -05:00
Author
Owner
Copy Link

@jrucker2004 commented on GitHub (Feb 17, 2026):

I didn't see it discussed above, but bulk moving tasks between projects would be nice to include. If it is different enough from bulk editing, I'm happy to create a new feature request, please let me know.

<!-- gh-comment-id:3917677565 --> @jrucker2004 commented on GitHub (Feb 17, 2026): I didn't see it discussed above, but bulk moving tasks between projects would be nice to include. If it is different enough from bulk editing, I'm happy to create a new feature request, please let me know.
GiteaMirror commented 2026-04-20 16:09:21 -05:00
Author
Owner
Copy Link

@FoxxMD commented on GitHub (Mar 4, 2026):

The implementation of #115 was a huge leap forward in easy task management which is greatly appreciated ❤️ but bulk movement would also be appreciated. multi-select drag and drop would be the nail in the coffin on this particular ui/ux issue.

<!-- gh-comment-id:3997740857 --> @FoxxMD commented on GitHub (Mar 4, 2026): The implementation of #115 was a huge leap forward in easy task management which is greatly appreciated ❤️ but bulk movement would also be appreciated. multi-select drag and drop would be the nail in the coffin on this particular ui/ux issue.
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 area/task-editor area/task-metadata
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#5820
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?