Behaviour of drag'n'drop in the dashboard (tours, group, multiselect and linked tasks (= deliveries, multidropoff))))

[Atala]

👋

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 ^_^

• shall we be able to move individual tasks outside from group to courier? for now you can move only whole group ( #3953 )
• shall we be able to move individual tasks outside from tour to courier? for now you can move only whole tour ( #3953 )
• when reordering a task in a linked tasks/deliveries we shall move only this task or all the linked tasks in order? (= dropoff before pickup)
• when multiselecting tasks then assigning tasks shall tasks be in (1) selected order (current) or (2) order in the "unassigned panel"

Current behavior	Proposed behaviour
Task cannot be moved individually outside tour	We can move individual task outside tour
Task cannot be moved individually outside group	We can move individual task outside group
We cannot assign a group to a tour	We can assign a group to a tour
Tasks are assigned in the order they are selected	Tasks are assigned in the order they are selected (no change)
Multiselect is kinda working only from the "Unassigned panel"	You can multiselect from all columns (inside tour, groups, ..) and all tasks are moving together

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 ?

[Paul-Eraman-CoopCycle]

Responses based on our workflow:

1. I think we should have a "lock" button for tours. A problem with CoopCycle currently in a UI sense is that I never am sure if i am in an editing mode or viewing mode (look at the task modal in the admin panel for example). When working on a bike it is easy to move something by accident and create problems for couriers. I think a lock button both allows for the needed modification of tours as new orders come in, but also gives a sense of security when moving tours around, reassigning, etc
2. worth asking other people who use groups (but not as a beta version of tours) how they use it
3. don't see why not
4. agree
5. I propose a UX "rule" for CoopCycle: drag and drop on task of an order/delivery moves the associated tasks of the order/delivery; right-click actions only effect that task
   this way we maintiain the fast on the fly drag and drop UX we use for food delivery (very useful) but allow for more details, granular actions as well (for local commerce and last mile)

[Atala]

Please specify what you want for the "lock" feature, because I think you want a lock only when the tour is assigned, not when you are building the tour.
not here but in a github issue please

[Atala]

OK for (5) I will look into it

[Paul-Eraman-CoopCycle]

I would want the lock function to work wherever the tour is, no matter if assigned or unassigned

[Atala]

OK. to be discussed in a specific github issue and prioritized

[0bi0ne1312]

Thanks for all that work !

1. / 2. We should but I agree with paul about the potentiality of a lock button I should be able to move tasks once a tour assigned
2. really useful when we need to reassign a task and we want to keep the historic of who did what (in a multi drop-off tasks for example)
3. Yeap agree !
   5.from the table, everything proposed is good for me (right panel) and I can't wait to have these on ! Especially to be able to move group to tour. I use both and it is really useful to me not to have to ungroup something to put it in a tour...
4. For the linked tasks, even if it is sometimes useful to move linked tasks in one move, sometimes it is not and it is like you have different behavior if it a linked one or not... Perhaps making things "simpler" is better : you select one task, you move one task, if you select more, you move everything in the order you select these ?

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 !

[Atala]

To be discussed in dedicated issues :

• lock tours and whatnot
• managing tours on a bike

As for linked tasks I think the best behavior is the current one :

• assign also linked tasks when assigning a task
• add linked tasks to tour when adding a task to a tour
• do not move linked tasks together when reordering

so it works for foodtech (assign fast restaurant pickup + customer dropoff) and can be modified easily for shops (multi dropoff deliveries).

[fortyoneandahalf]

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

[Atala]

• OK I will do the capability to drag a single task, actually it is on my assigned issues for the next days
• OK for linked tasks, I implemented what I said above and I think it is good
• yes actually I noticed that as well, I create the issue. Can the other tell us if it is important to them ?

PS : who are you? can you put your real name (or at least firstname) on your profile? so I can see who I am talking to ^^ (github is linkedin for developers it is serious shit lol)

[Atala]

@fortyoneandahalf I created issue here coopcycle/coopcycle-web#3969 and Paul will prioritize it when he wants

[fortyoneandahalf]

This is Phil from tricargo, apparently I can't update my GitHub profile on mobile but I'll edit it later.

And I don't class myself as a dev anymore, so I don't have to take GitHub so seriously 😜

[rayon9coop]

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
We can move an individual task outside a group -> Yes
We can assign a group to a tour -> Yes
Tasks are assigned in the order in which they are selected (no change) -> Yes
You can make a multiple selection in all columns (tour, group, ...) and all tasks are moved together -> Yes

In addition, drag-and-drop selection of a linked task (eg. pickup without dropoff) could be a first step towards this issue

[Atala]

@rayon9coop yes this issue will be solved by what i am currently doing. we just need to agree on when the linked tasks are moved together.

[Atala]

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

[Atala]

yes it is aubin case above : you have linked task (either complete or partial) in a tour. so you are in the lastmile case you gave: a lastmile dispatcher picked carefully the tasks they wanted to move (they created a tour). so in this case you dont want to force linked task I guess?

also there is a bug in Aubin's case is that the linked tasks order is not preserved when moving both (issue coopcycle/coopcycle-web#3983 )

[0bi0ne1312]

I am just saying it is useful to move linked tasks together...

[Atala]

after discussion with paul :

• move order/linked task when moving with dragndrop from unassigned to group, tours, courier
• move order/linked task when moving with dragndrop from courier to unassigned,group, tours
• do not move order/linked task that are unassigned when moving tour with dragndrop

[rayon9coop]

Hello @Atala : not sure i get what you said just ahead. Could you explain in french please?

[Atala]

L'idée est que le dragndrop (interface accessible, utilisateurs "débutants" ou pressés) continue à bouger les tâches liées à l'assignation vers un groupe, un tour ou un coursier
Les tâches peuvent être déliées en assignant via le menu clique droit ou en assignant le tout en dragndrop puis en désassignant une tâche spécifique

Pour le cas d'aubin spécifiquement (gif dans la conversation slack ci-dessus), les tâches liées étaient organisées dans la tournée mais l'ordre change quand on assigne la tournée c'est un bug que je vais fixer