Imagine you have an ownership queue that has both a rule for Account ownership and Contact ownership with rules logic of "1 OR 2". Currently if there is a match for both rules, the assignee is chosen based on who is first in the physical order of the reps in the queue's assignee list. This means that if the Contact owner is listed first they will be assigned the meeting even if the Account owner matches and the rules logic lists the Account ownership rule first. This also means that in order to guarantee that Account ownership is prioritized over Contact ownership that two separate ownership queues must be created.Instead, what I propose is that we determine the assignee in these situations based on the rules logic. If the first rule is for Account ownership, the second rules is for Contact ownership, and the rules logic is "1 OR 2", then it should route to the Account owner because that rule is listed first in the rules logic. This will eliminate the need for customers to create multiple ownership queues and create a more intuitive setup.Reference this JIRA: https://floatingapps.atlassian.net/browse/CPP-6856