I have created quick patch to query.rb to fix this issue, please find it attached. Please note, that i tried to keep modifications tiny, so 'author_id' field affected as well.
--------------------------------------------------------------------------------
+1
now you can not combine "asssigned to nobody" filter with "assigned to me"
--------------------------------------------------------------------------------
Vitaly Klimov wrote:
> 'author_id' field affected as well.

Can you explain how was it affected please?

--------------------------------------------------------------------------------
Nikolay Kotlyarov wrote:
> Can you explain how was it affected please?

It's "affected" since author and assignee use the same list of possible values. But it's not the correct behavior, since author cannot be none, I think it would lead to an other defect :)

I'd prefer a generic solution which would consist in having a "<< none >>" option in some fields : assigned to, target version, category, etc. But only when it makes sense.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
Please can be this functionality merged into trunk?
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
nice reaction time...
it would be also great to have an "auto-assign" feature without doing categories...
--------------------------------------------------------------------------------
Wished I had this feature today! What can we do to pick this up again?
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
+2 At least two users at our company wish this feature. This ticket was created 8 years ago, a solution seems to be attached, so maybe priority should be reconsidered?
--------------------------------------------------------------------------------
+1

--------------------------------------------------------------------------------
Which will be the difference between "Assignee None" and "Assignee Is <nobody>"?
--------------------------------------------------------------------------------
Marius BALTEANU wrote:
> Which will be the difference between "Assignee None" and "Assignee Is <nobody>"?

I think the difference is that with <nobody> you can achieve a kind of OR combination.
Assigned to _somebody_ *OR* _nobody_...

I also can't imagine a useful situation for that but there seem to be one.
Perhaps someone of the folks who back this feature could explain its specific use case.

--------------------------------------------------------------------------------
wow, 8 years, good that I'm still alive :-) The difference is already explained in the description of the ticket.
The usecase I don't remember right now, sorry. I guess one could be: "I want to see issues assigned to me (that I'm working on) + the queue (so I can see what's not been picked up yet and I could pick up)"
--------------------------------------------------------------------------------
Radek Antoniuk wrote:
> wow, 8 years, good that I'm still alive :-) The difference is already explained in the description of the ticket.
> The usecase I don't remember right now, sorry. I guess one could be: "I want to see issues assigned to me (that I'm working on) + the queue (so I can see what's not been picked up yet and I could pick up)"

Got it, thanks.
--------------------------------------------------------------------------------

relates,New,5115,Assignee & Target version issuelist filters: allow to specify multiple selections (e.g. x OR blank)
duplicates,Closed,28924,Issues filter: Adding a <<Nobody>> special entry to the user list