Routing to queues based on contact_location or asset_location

You can do that with an Incident rule. 

Under the "Set these properties" section add an "<Advanced assignment>" for "workitem_assigned_to_worker_id" = (id of queue you're assigining to)

On the "When" section it's up to you, but I'd make it say something like this:

When ALL of these are TRUE
     "Assigned worker" is equal to "[unassigned]"
     When ANY of these is TRUE
          "Asset Location" contains "London"
          "Contact location" contains "London"
     <end>
<end>

Make sure to make it active and (in most cases anyway) remove the Terminal option.

Hi MBHarmon,

thank you for your feedback.

Your rule works fine, but didn't help me in my case.

I've several locations (London, Amsterdam, Hamburg...) For each location i've written one incident rule.

first incident rule is your rule
2. incident rule is the same only with changed locations for contact and asset.
...

If we created an Incident with an contact with contact_location "London" and the asset_location "Amsterdam" the incident will be assigned to the Queue "Level1_Amsterdam". Thats not ok, Level1_London must be assigned, because the contact_location ist the most important than the asset_location.

If Contact_Location = London then ignore asset_location and assigned queue to Level1_London
   else 
     use the field asset_location and assigned the incident to the appropriate queue for the asset location

With the terminal option I can solve this error, but ervery other incident rule will then not fire (we use Incident rules to set the dure dated based on the priority) Terminal is no option for us.

Can your idea be implemented into one ore several routing rules?

Thank you very much.

regards,

Eisenkarl