[{quoted}](name=That Evelynn,realm=NA,application-id=3ErqAdtq,discussion-id=RjAfMExc,comment-id=0002000000000000,timestamp=2016-02-13T22:12:04.871+0000)
That's what it does, though.
I go jungle/support and it makes me support, and then it throws the mid/jungle into the jungle role.
My role was available. But it shoved me into support instead of waiting for a real support, and then threw someone else into jungle who had it marked as secondary. In that scenario it also shuffles a bunch of other people into their secondary roles as well to compensate (usually 3-4 people will end up in their secondary roles when it does that).
There are several aspects to your argument that are lacking, primarily, the fact you are basing the entire system on your own expectations. For myself, when I utilized it I played my primary role the majority of the time. The only time this changed was when I switched my second from mid, to support, or to top, where I saw myself playing those two positions more often.
Let us consider, however, your observation is universal.
What is occurring in the background? We understand the system needs to place 5 individuals on a team capable of playing a variation of 5 spots. In the event you have several individuals aiming for the same spot, the system may be choosing at random from the three individuals who have chosen the designated role, and then placing the other two in their other chosen roles.
Essentially
Player 1 Chooses A/B
Player 2 chooses A/C
Player 3 chooses D/A
Three people have A selected, so the system resolves the issue by choosing at random.
Which would make sense and be fair since in the end, even if it considered primary only in this scenario, either player 1 or 2 would get the spot anyway.
As it stands, we don't have an understanding of the internal workings of the system created, but one can guess, it isn't really broken.
It just doesn't have the same function as team builder which gives the preferred role out, it sorts between two which makes it more complicated.
