Opened 14 years ago
Closed 14 years ago
#9670 closed defect (worksforme)
TracQuery doesn't work with values that contains spaces
Reported by: | shesek | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 0.12 |
Severity: | normal | Keywords: | tracquery |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When using the (top right) search box to search for query:milestone=not applicable
it looks for 'milestone=not', while ignoring the 'applicable' part. Also, there doesn't seem to be a [query:]
syntax to allow that, as the 'applicable' is considered the anchor ([query:milestone=not applicable]
).
For the search box it can be fixed by considering any string until an '&' or '|' as the value, not quite sure about how it can be handled with [query:]
.
Maybe spaces just shouldn't be used in milestones names? t.e.o does use 'not applicable'…
Attachments (0)
Change History (2)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Oh, cool, I didn't know about that. Closing as worksforme, sorry for the noise :-)
How about
query:"milestone=not applicable"
? Seems to work here.