Opened 18 years ago
Last modified 9 years ago
#4398 new defect
Inconsistent search for single-digit tickets
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | search system | Version: | 0.10 |
Severity: | minor | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal 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 (0)
Change History (6)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
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'.
follow-up: 4 comment:3 by , 18 years ago
Milestone: | → 0.10.4 |
---|---|
Severity: | normal → 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 by , 18 years ago
Replying to cboos:
Still,
!#1
gives you the 'search query is too short' error…
Sure, it was just a workaround
comment:5 by , 17 years ago
Milestone: | 0.10.5 → 0.12 |
---|
comment:6 by , 9 years ago
Owner: | removed |
---|
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.