coopcycle / coopcycle-web

Logistics & marketplace platform. Only for worker-owned business.
https://coopcycle.org
Other
571 stars 130 forks source link

Deprecate recurrence rule creation from the dispatch panel #4558

Open Atala opened 3 months ago

Atala commented 3 months ago

Image

Original post:

  • Hide away recurrent rules in some dropdown (Vladimir: won't do for now)

  • Do not tied these rules to a store (Vladimir: won't do for now)

  • Simplify things in the form (Vladimir: only view existing rules)

  • We will support multiple pickups as an order later, now multiple pickup is not a delivery just a bunch of task

  • We will support one pickup as an order later

  • From the dispatch in a hidden dropdown, users can create recurrent rules that don’t create orders (Vladimir: won't do for now)

  • Vladimir will add a toggle on/off for subscriptions/recurring orders to be created automatically or manually; https://github.com/coopcycle/coopcycle-web/issues/4716

  • Vladimir will migrate the "task recurrent rules" to "subscription"

Paul-Eraman-CoopCycle commented 1 month ago

What things are only one pickup? For me, these subscription things exist for the types of orders that are frequent, but uncertain until day of (which is different from definitely always on mondays, which is recurrent rules)

Atala commented 1 month ago

rayon9 stuff ahah

Paul-Eraman-CoopCycle commented 1 month ago

ill talk to him, i think he is asking for a workflow we are not considering supporting

vladimir-8 commented 1 month ago

If I remember correctly they are using tasks for 'internal' stuff, like oiling the bike etc.

Paul-Eraman-CoopCycle commented 1 month ago

Yeah, but they could make a multidropoff order to do the same

Ex: Pickup is "enter shift" Dropoff 1 is "dont forget helmet" Dropoff 2 is "finish shift"

vladimir-8 commented 1 month ago

Of course, you can make such fake orders, but then you'll need fake stores and probably filter them out from regular orders, exclude them from invoices, billing, etc.

While a task seems like an appropriate place unless somebody wants to include them in accounting somehow

Paul-Eraman-CoopCycle commented 1 month ago

We have a "eraman orders" store for orders made by random peopel and a "eraman testing" for trying stuff out. seems ok to me

not going to worry about accounting here honestly :/ if people use CC for non logistical stuff i dont think we can afford to design for that currently...