Open gavinwahl opened 7 years ago
The old buggy supported these searches with special syntax in the search field:
assigned:foo
foo
me
created:foo
involved:foo
project:foo
f.*o.*o.*
state:resolved
priority:high
"foo bar"
#:123
!filter
filter
The filters combine:
So assigned:foo assigned:bar priority:high parses as (assigned:foo OR assigned:bar) AND priority:high.
assigned:foo assigned:bar priority:high
(assigned:foo OR assigned:bar) AND priority:high
!assigned:me involved:me is (NOT assigned:me) AND involved:me
!assigned:me involved:me
(NOT assigned:me) AND involved:me
#:123 #:456 #:789 is #:123 OR #:456 OR #:789.
#:123 #:456 #:789
#:123 OR #:456 OR #:789
Is the way filters of the same type combine compatible with AND and OR conditions?
what should assigned:a assigned:b (assigned:c AND priority:high) parse as?
assigned:a assigned:b (assigned:c AND priority:high)
The old buggy supported these searches with special syntax in the search field:
assigned:foo
search for bugs assigned to someone with a name offoo
.me
is an alias for the current user.created:foo
involved:foo
searches for bugs thatfoo
has created, commented in, mentioned in, or been assigned to.project:foo
searches for bugs in projects whose title matches the regexf.*o.*o.*
state:resolved
priority:high
"foo bar"
fulltext searches for foo immediately followed by bar, ie phrase search#:123
filters for bug number 123!filter
negatesfilter
The filters combine:
So
assigned:foo assigned:bar priority:high
parses as(assigned:foo OR assigned:bar) AND priority:high
.!assigned:me involved:me
is(NOT assigned:me) AND involved:me
#:123 #:456 #:789
is#:123 OR #:456 OR #:789
.