Page MenuHomePhabricator

go to bug#? who can remember numbers for bugs?
Closed, ResolvedPublic

Description

Author: kissall

Description:
I bet many people tried at least once (I did several times)to put a bug name into go to
bug# box and search it. I have to click "Search bugs" each time to do what I really
want.
Wouldn't it more intuitive to put search box accepting a bug name here instead of a
accuate number for a particular bug?


Version: unspecified
Severity: enhancement

Details

Reference
bz519

Event Timeline

bzimport raised the priority of this task from to High.Nov 21 2014, 6:55 PM
bzimport set Reference to bz519.
bzimport added a subscriber: Unknown Object (MLST).

river wrote:

You can search using the box on the main page.

kissall wrote:

Oh, yes. Thank you very much.
And how about the box in the navigation bar? It still does not accept
a name for a bug right now.

(In reply to comment #1)

You can search using the box on the main page.

Currently when trying to put text in the search box in the sidebar, bugzilla comes back with this ugly message:

Invalid Bug ID

The 'bug number' is invalid.  If you are trying to use QuickSearch,
you need to enable JavaScript in your browser. To help us fix this
limitation, add your comments to bug 70907.

So clearly this is *intended* to work (so long as JavaScript is enabled) but something isn't working. Timwi, can you check if there's
some JS bit missing from the template?

timwi wrote:

No, the JavaScript is perfectly in place. Some people on MediaWiki-General have
reported that it works for them.

Changed these lines in useful-links.html.tmpl:

<script type="text/javascript" language="JavaScript" src="localconfig.js"></script>
<script type="text/javascript" language="JavaScript" src="quicksearch.js"></script>
<form name="searchform" id="searchform" method="get" action="show_bug.cgi" onsubmit="QuickSearch(searchform.id.value);

return false;">

Seems to work for me now.

Timwi, was that before or after I added the JavaScript to the template? ;)