Comment 4 for bug 519034

I agree with Ana, running the scheduler to mark a order as "picked" has no mean. The scheduler doesn't pick materials, right? The scheduler doesn't make a order finished.
In several cases you, like Ana mentioned, you don't want to run the scheduler. A other example is a trade company with 60000 constantly changing products. They don't use the scheduler function, but manual procurement due to the fact that they can not maintain the minimal stock records, that is mandatory to have for the scheduler.

i.m.h.o the scheduler should not be in charge of setting order statusses for order is picked and putting the order status from in progress to another state. That's to late, it should be done by a workflow action, like the picking itself.
Wherefore do have workflow actions? For executing triggers I thought, including user-permissions.

this is a regression and I can not understand that a change like this is not communicated as it seems that it is changed not by accident!
Imaging you have procedures defined in you company that are based on the picking and order status, e.g. for invoicing. If you are not aware of such a change you will run directly into problems. When one discovers this change, you have to change internal procedure.
At least you want to know upfront so new procedure could be implemented upfront.