Logged In: YES 
user_id=6405

I've finally manage to reproduce the error. If I switch the "from" 
table names in the O.P's SQL, it works fine (ie. "from 
issue_nosy,_issue") but if they're around the other way (ie. "from 
_issue,issue_nosy") then I get an error. 
 
I believe this has been fixed since the SQL generation now 
always puts the _issue table (or whatever the class table is 
called) last in the from list.