Ticket #4597 (closed defect: fixed)
search does not find id:0
| Reported by: | CharlesNepote | Owned by: | team |
|---|---|---|---|
| Priority: | minor | Component: | Core |
| Version: | latest | Keywords: | search id 0 |
| Cc: | charles@…, skyper |
Description
Finding all modifications during a month for a given zone is very interesting. Search for "timestamp:2010-02" was working fine but no longer works in version 3033.
Attachments
Change History
comment:2 in reply to: ↑ 1 Changed 2 years ago by CharlesNepote
Replying to jttt:
You can try timestamp:"2010-02" (not tested)
Yes it works! But you have to know it...
Either it must be documented. Either "timestamp:2010-02" should be accepted.
I prefer the second solution.
comment:3 Changed 2 years ago by mjulius
Ticket #4621 has been marked as a duplicate of this ticket.
comment:4 Changed 2 years ago by skyper
- Priority changed from normal to major
- Summary changed from Search for timestamp:2010-02 no longer works to Search broken and search documentation outdated
I can not find id:0.
nor can I find "FIXME": through search.
I tried all possibilities, but I get no result.
comment:6 Changed 2 years ago by bastiK
works for me (3044): Type FIXME or FIXME=*
Bug: The latter is case sensitive although the option is unticked.
(I can confirm id:0 is broken.)
Replying to Ldp (Ticket #4621):
Fine, but what does the number mean to the search compiler, in this specific case? Is this parsing just a byproduct of the generic parsing for the other search options that have numberic modifiers, like nodes: and timestamp: ?
I think it's a defect and should be fixed.
comment:8 Changed 2 years ago by skyper
- Keywords id 0 added
- Priority changed from major to minor
- Status changed from closed to reopened
- Resolution fixed deleted
- Summary changed from Search broken and search documentation outdated to search does not find id:0
comment:9 Changed 2 years ago by jttt
- Status changed from reopened to closed
- Resolution set to fixed
comment:10 Changed 2 years ago by skyper
Ticket #4741 has been marked as a duplicate of this ticket.



You can try timestamp:"2010-02" (not tested)