I ran across this issue as well, I am a item level 569 hunter and found that even when trying to click waitlist even on groups with item level requirement even as low as 550, it would state "Not Qualified".

And in reply to the above reply, it isn't due to the Role being unchecked, instead you get a different error, if I remember correctly, it says "incorrect role/class" or something similar to that.

oQueue keeps adding friends even when dark/disabled

I keep finding that in this new version of oQueue (2.0.1), that it keeps adding people to my friends list (mesh?) even after I have clicked Remove Battle Tag, Remove All oq B-net added friends, and Go Dark.

So then I have to reopen oQueue and click the Remove all oq b-net friends button again and Go Dark again, for it to only add someone new sometime later during the day.

It isn't constant or very much to be much of an annoyance, not sure what causes it (maybe region changes during my gameplay?), but it seems every few hours or so I open my friends list to whisper a friend only to find a new name in there that doesn't belong or sometimes get b-net whispered by someone asking me who I am (people who don't know that oQueue adds people)..

Before in older versions when I had clicked all 3 of those buttons (particularly Go Dark/Disable), I'd never still continue to get friends added over the day.

Now when I want to "go dark", I have to use my Add-On Manager addon to fully disable oQueue.

OQUEUE KEEPS HIJACKING CHAT CHANNEL

one of the annoying OQueue does from time to time is hijack the General Chat Channel which causes every other channel to be pushed up 1 number: i.e. General chat becomes /2, Trade is /3, Local Defense /4, etc.. This is very annoying and forces me to fly to a main city, delete all the channels, then have to readd each one, one by one.

OQueue should not be stealing channel 1.

I can only hypothesize that this happens because OQueue intilizes/loads before WoW had a chance to load and connect to the chat channels. So in these instances, OQueue gots first dibs on chat channel 1.

So to remedy this, possibly could some coding be added to OQueue to delay by a few seconds in the creation/connection of it's custom chat channel to prevent this from happening?