Force Queue move on tickets in Raw

[brensly]

Hello,

As per the default setting, any tickets not triggering any postmaster filters will land in the Raw queue which is fine.
Although we have instructed our agents to always move tickets from Raw queue to another queue as a first action, every now and then they forget.
We would like to force our agents interacting with tickets in the Raw queue to move the ticket to another queue before performing any other action such as replying, adding notes or closing the ticket.

Is this possible, and if so, how?

[crythias]

Maybe your workflow is too complicated ...
If the first action a user has to do is move a ticket from bucket a to bucket b, perhaps it may be more proactive to have the tickets land in bucket b.

Queues are designed for groups of agents that can handle a categorization of tickets. If you need to accept all tickets via email but you have no way to categorize them because you need to after they arrive, I would *possibly* set an ACL where no action is permissible if queue is still in Raw. Of course, you now need to change/move ticket before assigning owner as a separate thing to do, but this is already complicated.