Ticket #4398 (new defect)
Opened 5 years ago
Last modified 4 years ago
Inconsistent search for single-digit tickets
| Reported by: | eli.carter@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-0.1X |
| Component: | search system | Version: | 0.10 |
| Severity: | minor | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
If you search for #1 in the search field, you will jump to that ticket. If you try to search for #1 on the search page, you get an error that the search term is too short. (So you'll get that error on the first 9 tickets of the project.)
It is also useful to search for tickets that reference a ticket number; perhaps the search page should do that instead.
Attachments
Change History
comment:1 Changed 5 years ago by eli.carter@…
comment:2 in reply to: ↑ description Changed 5 years ago by eblot
Replying to eli.carter@commprove.com:
It is also useful to search for tickets that reference a ticket number; perhaps the
search page should do that instead.
You can search for occurence of tickets using the ! character to escape the quickjump feature, for ex: !#45 will search for all occurences of '#45'.
comment:3 follow-up: ↓ 4 Changed 5 years ago by cboos
- Milestone set to 0.10.4
- Severity changed from normal to minor
Still, !#1 gives you the 'search query is too short' error…
There are two issues raised here:
- the consistency of the quickjump behavior
- how to find the tickets that references a ticket with only one digit, without getting hit by the minimal length check
For 1., I think the fix is easy (setting 0.10.4 for that).
For 2., it would be cumbersome to fix and I think that this functionality is better achieved with TracCrossReferences than by a search over the entire database (e.g. searching for #1, you'll miss all the ticket:1 references; not with proper cross-references management).
comment:4 in reply to: ↑ 3 Changed 5 years ago by eblot
Replying to cboos:
Still, !#1 gives you the 'search query is too short' error…
Sure, it was just a workaround
comment:5 Changed 4 years ago by cboos
- Milestone changed from 0.10.5 to 0.12



t.e.o exhibits this behavior, as does a 0.10 install. Sorry, I don't have a 0.10.3 or 0.11 handy to try.