Entering a number without # in search should find that ticket

[morris]

For example entering 28 or #28 in the search box should show ticket #28 in the search results.

[morris]

Entering #nn works fine, but it would be nice if the the ticket was in the the result set even if a plain number like 28 was entered. Newbies don't know they have to enter the #.

[Emmanuel Blot]

-1: I don't think so: why ticket should be prefered over changesets, for example?

Newbies probably need to read the manual first, or to use the "view ticket" feature to look for a ticket.

[sid@…]

-1 as well — I look for changesets as often as I look for tickets. using the r or # prefix is easy enough.

One thing to note though is that if you put just a number in the search field, and select only changeset search results, you don't get that changeset number in your results. For example, ​this query to search for changeset 1024 using just number does not return changeset:1024 in the results.

It looks like the same problem exists with ticket searching.

[Matthew Good]

Replying to eblot:

-1: I don't think so: why ticket should be prefered over changesets, for example?

I don't think the request has to be specific to ticket numbers. I think it could be made generic so that all searchable items search for matching identifiers, not just the descriptions.

[Christian Boos]

Replying to mgood:

I don't think the request has to be specific to ticket numbers. I think it could be made generic so that all searchable items search for matching identifiers, not just the descriptions.

Exactly, and those results could be displayed in the same way the results for quickjump are now displayed: example search for "1024" (the real thing would also list ticket 1024 as a quickjump link and provide this result when searching for the "1024" string).

Schedule that for 1.0 (advanced search).

[Christopher Lenz]

This is a duplicate of #1268 if I'm not completely mistaken.