Behaviour of drag'n'drop in the dashboard (tours, group, multiselect and linked tasks (= deliveries, multidropoff)))) #12
Replies: 6 comments 17 replies
-
|
Responses based on our workflow:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for all that work !
Also something not mentionned but perhaps it is not the good issue for it : being able to access the tour panel on the phone... If I am on the bike dispatching (I am not supposed to but anyway) I cannot access this panel so I am a bit stressed to make tours in advance for now in case I need to go on the road in the middle of my shift. Have a nice day ! |
Beta Was this translation helpful? Give feedback.
-
|
To be discussed in dedicated issues : As for linked tasks I think the best behavior is the current one :
so it works for foodtech (assign fast restaurant pickup + customer dropoff) and can be modified easily for shops (multi dropoff deliveries). |
Beta Was this translation helpful? Give feedback.
-
|
Being able to drag and drop a grouped task on its own without having to ungroup or to switch to a different view would be excellent, we have this scenario all the time. With tours it might happen less often but I think it would also be useful to be able to drag and drop a single task. Could we consider perhaps that dragging a task just moves that single task, whereas dragging the group/tour header moves the whole group/tour? Linked tasks: no strong opinion, I think both moving a task on its own and moving it together with linked ones are important functions to have, so long as we pick a rule about what drag and drop does and stick to it across the platform I'll be happy enough. One thing that you didn't mention but might be relevant here: it's not currently possible to drag and drop assigned tasks directly from one courier to another inside the assigned panel and this is a thing that would be very useful to us (that may be in a GitHub issue somewhere, I don't remember). |
Beta Was this translation helpful? Give feedback.
-
|
In general, task selection and movement behavior should not be linked to the nature of the task or its membership of a group, tour, etc., or its connection with another task (drop linked to a pickup). We can move an individual task outside a tour -> Yes In addition, drag-and-drop selection of a linked task (eg. pickup without dropoff) could be a first step towards this issue |
Beta Was this translation helpful? Give feedback.
-
|
follow up of slack discussion @Paul-Eraman-CoopCycle so it appears that linked tasks are to be moved together in very special cases to not get in the way of power user, so I propose : "linked tasks are forced moved together only when dragndropping 1 task from the "unassigned task" column" (so it doesnt force move with tours and with multiselect which we could call power user stuff) tell me if you have other cases in mind |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
👋
as I had some feeling that people would want more from tours... (+ some issues with multiselect). I started cleaning (on my machine) the way we handle dragndrop of tasks on the dashboard so maybe we can clean this.
Below I write some questions + actual behavior, feel free to tell me the expected behaviour of what you want to change! I think with the code I have I can adapt to all answers, but you never know before you try ^_^
Linked tasks (= deliveries, multidropoff)
for now without tours : when you assign or unassign linked tasks they are moved together
with tour : doesn't work yet
-> shall we keep this (complex) behavior for tours ?
Beta Was this translation helpful? Give feedback.
All reactions