Batch task operations #1768

New Issue

W-Floyd · 2021-03-27T19:04:30Z

W-Floyd commented

2021-03-27 19:04:30 +00:00

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).

👍 3

konrad added the

kind/feature

label 2021-03-28 14:40:15 +00:00

konrad commented

2021-03-28 14:40:52 +00:00

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

👍 4

dpschen referenced this issue from vikunja/frontend

2022-02-14 10:22:49 +00:00

Manipulate many tasks #1896

xeruf commented

2022-07-08 15:11:55 +00:00

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 referenced this issue from vikunja/frontend

2022-08-11 09:13:02 +00:00

Set Default Bucket for new Kanban tasks #1968

xeruf commented

2023-03-30 01:18:36 +00:00

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!

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

2023-03-30 09:59:30 +00:00

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:

If clicked item is unselected, mark it as selected.
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).

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

2023-09-03 18:28:32 +00:00

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.

> 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.

konrad referenced this issue from a commit

2024-02-07 14:00:33 +00:00

chore(deps): update dependency caniuse-lite to v1.0.30001325 (#1768)

Sign in to join this conversation.