mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-22 06:11:08 -05:00
Bulk edit for tasks #25
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vikunja#25
Reference in New Issue
Block a user
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?
Originally created by @svigneau on GitHub (Jan 1, 2022).
It would be useful to enable bulk edit for tasks. This could be used, for instance, to reschedule multiple tasks at once.
@dpschen commented on GitHub (Jan 3, 2022):
See: https://kolaente.dev/vikunja/frontend/issues/445
@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:
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.
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:
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:
xeruf commented on 2023-09-03T18:28:32.000Z:
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.