I think I can use awesome binary logic to write this as:

not-responsible:any not-milestone:any

But it'd still be nice to know if I can use OR. Thanks!

Edit: Actually that doesn't return what I expected - it turns it into responsible:none milestone:none (i.e., using AND).

OR should work. I tested it on our own internal LH and I didn't see that it treated it OR like a search string.

Can you screenshot your search results?

Thanks,
Nicole

http://skitch.com/wuputah/dfwbn/lighthouse-or-query

You can see that:

1. The text indicates it's doing a text search: Displaying all 12 entries for unassigned tickets matching 'OR', not in a milestone, sorted by updated.
   
2. The number of results (12) is much less than the Unassigned (65) or No Milestone (50) shared ticket bins that I created. Naturally, there should be at least 65 results.

I tested on our site, I tried to sort for tickets with either tag. I tried tagged:wpf tagged:silverlight. It came back as AND

I tried OR between them it treated the OR as a string text
I also tried with or same as OR

Is there any estimate when Boolean "OR" in search will be implemented?
It doesn't work. You have screen shots from jdance, I can send you screen shots from my projects if you want.

I too am VERY eager for OR support as well as some ability to group search predicates.

I'll give you a use case: We're using one of our LightHouse projects as a high level project management tracker with GTD-like milestones that have implicit due dates like "Today", "This week", "Next week" and "Someday" (i.e. Explicit due dates would have to be constantly changed which is out of the question)

I'd like to be able to create a shared "Overdue items" search bin that looks something like this:

state:open ((milestone:Today -created:"today") OR (milestone:"This week" created:"before this week") OR (milestone:"Next week" created:"before one week ago"))

The explicit OR operator and parenthentical groupings would seem to be a critical requirement for such a query but I'm open to other ideas.

Just found another dire need for OR: In creating a triage ticket bin that is populated only with tickets that meet all of the following criteria:

• state:open
• milestone:none
• responsible:"Open Melody" OR responsible:none

Open Melody is the admin account for our identically named project and is the default ticket assignee for the project. When a new ticket would come in, it would automatically be assigned to Open Melody and magically appear in our triage bin..

However, best laid plans have been systematically and repeatedly laid to waste whenever a developer removes their own assignment to a ticket thereby allowing it to fall to the wayside out of our vigilant watch.

If we could do an OR search like so, the ticket bin would contain all of the open tickets not assigned to a milestone or a real person.

state:open milestone:none ( responsible:"Open Melody" OR responsible:none )

As it stands, we need an additional ticket bin for the alternate 'responsible' value.

Or, you know, I'd be just fine with http://lucene.apache.org/java/2_4_0/queryparsersyntax.html :-D