Reported by Stephen Leake, Oct 8, 2010
allow jumping directly to an issue by number. Either have the search engine recognize bare numbers in the search string, and treat them as issue numbers, or provide a separate entry box for numbers. A work-around is to edit the URL to enter the number; that works, but is not obvious.
Comment 1 by Patrick Georgi, Oct 30, 2010
idf-lookup-issues-by-id.diff provides direct access by id by entering "#id" or "id" in the search box. Possible improvements over this patch: - check for issue number before accepting it (ie. no nasty error if looking up a non-existing id) - with JS, add some (lightly colored) "full text search or issue ID" text in the empty search box, and remove it once the user selects the box, as a clue how it can be used.
Comment 2 by Thomas Keller, Oct 31, 2010
> with JS, add some (lightly colored) "full text search > or issue ID" text in the empty search box, and remove > it once the user selects the box, as a clue how it can > be used. Something like this? <input title="Text search or issue ID" value="Text search or issue ID" onfocus="this.value = this.value == this.title ? '' : this.value; this.style.color = 'black'; " onblur="this.value = this.value == '' ? this.title : this.value; this.style.color = this.value == this.title ? 'grey' : 'black';"> I'm not that good in jQuery, otherwise I'd probably moved that into an external three-liner initialized by some unobstrusive CSS class...
Comment 3 by Thomas Keller, Oct 31, 2010
Comment 4 by Thomas Keller, Nov 1, 2010
@Patrick: Proposal (as noted on IRC): * if a full-text search only results in a single hit, we could directly redirect to that * now when an issue number is given, this would just be a special query which could end in the same result: - 0 results if no issue is found - 1 result + redirection, if the issue is found
Comment 5 by Thomas Keller, Jan 6, 2011
@Patrick: Are you up for the remaining improvements?